Triple
T19017815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meuse-Argonne region |
E465400
|
entity |
| Predicate | majorOffensiveEndDate |
P20879
|
FINISHED |
| Object | 1918-11-11 |
—
|
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: 1918-11-11 | Statement: [Meuse-Argonne region, majorOffensiveEndDate, 1918-11-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorOffensiveEndDate Context triple: [Meuse-Argonne region, majorOffensiveEndDate, 1918-11-11]
-
A.
lastMissionEndDate
Indicates the date on which the most recent mission associated with the entity was completed or ended.
-
B.
endDateOfMajorBattle
Indicates the calendar date on which a major battle or significant military engagement came to an end.
-
C.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
D.
battleEndDate
chosen
Indicates the date on which a specific battle or military engagement concluded.
-
E.
finalDefeatDate
Indicates the date on which an entity was ultimately and conclusively defeated.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6dc0f9081909cddc5186603e885 |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.