Triple
T25478874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ijzer |
E638509
|
entity |
| Predicate | wasFrontLineIn |
P117051
|
FINISHED |
| Object | World War I |
—
|
NE NERFINISHED |
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: World War I | Statement: [Ijzer, wasFrontLineIn, World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFrontLineIn Context triple: [Ijzer, wasFrontLineIn, World War I]
-
A.
frontLineDuring
chosen
Indicates that an entity is positioned at or serves on the front line during a specified time or event.
-
B.
frontLine
Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
-
C.
isFrontlineUnit
Indicates that an entity functions as a primary combat or operational unit positioned at or near the front line of engagement.
-
D.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
E.
frontlineAdvance
Indicates a movement of military or conflict front lines forward into previously uncontrolled or enemy-held territory.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f7737a1c81909933c73eacdfd6a8 |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:27 p.m.