Triple
T9124397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Civil War in France |
E218936
|
entity |
| Predicate | dateOfEventAnalyzed |
P830
|
FINISHED |
| Object | 1871 |
—
|
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: 1871 | Statement: [The Civil War in France, dateOfEventAnalyzed, 1871]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfEventAnalyzed Context triple: [The Civil War in France, dateOfEventAnalyzed, 1871]
-
A.
dateOfRelatedEvent
chosen
Indicates that there is a specific date on which a related event associated with the subject occurs or occurred.
-
B.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
C.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
D.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
E.
dateOfSituationAddressed
Indicates the date on which the situation, issue, or circumstance being referred to is (or was) addressed or dealt with.
- F. None of above.
Provenance (3 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8b7436c8190b45bc6e4d6ec7066 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.