Triple
T4447348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schlieffen Plan |
E96321
|
entity |
| Predicate | dateOfFirstExecution |
P45365
|
FINISHED |
| Object | August 1914 |
—
|
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: August 1914 | Statement: [Schlieffen Plan, dateOfFirstExecution, August 1914]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFirstExecution Context triple: [Schlieffen Plan, dateOfFirstExecution, August 1914]
-
A.
firstPerformedOn
chosen
Indicates the date or occasion on which an action, event, or performance was carried out for the first time on a particular subject or object.
-
B.
hasExecutionDate
Indicates that an entity is associated with a specific date on which an execution or carrying out of an action, order, or sentence is scheduled or took place.
-
C.
firstReachedDate
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
D.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
E.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355d31e10819086590b9f828d50b0 |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.