Triple
T33265635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | France v. Turkey (Lotus case) |
E851637
|
entity |
| Predicate | originatingIncidentDate |
P203980
|
FINISHED |
| Object | 1926-08-02 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 1926-08-02 | Statement: [France v. Turkey (Lotus case), originatingIncidentDate, 1926-08-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatingIncidentDate Context triple: [France v. Turkey (Lotus case), originatingIncidentDate, 1926-08-02]
-
A.
immediateCauseDate
Indicates the specific date on which an event or condition directly caused another event or outcome to occur.
-
B.
incidentTime
Indicates the specific time at which an incident or event occurs.
-
C.
injuryOccurredAt
Indicates that an injury took place at a specific location or during a particular event or time.
-
D.
sufferedEventDate
Indicates the specific date on which an entity experienced or was affected by a particular event.
-
E.
attackDate
Indicates the calendar date on which an attack or assault event took place.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0303622ce08190b359c9d247268729 |
completed | May 12, 2026, 10:39 a.m. |
| PD | Predicate disambiguation | batch_6a03030c02fc81908e546dba291b1240 |
completed | May 12, 2026, 10:38 a.m. |
| PDg | Predicate description generation | batch_6a03036152e4819082881a9f59919e1b |
completed | May 12, 2026, 10:39 a.m. |
Created at: May 1, 2026, 1:32 a.m.