Triple
T9870416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Loos |
E239940
|
entity |
| Predicate | frontlineLengthApprox |
P38466
|
FINISHED |
| Object | about 11 km |
—
|
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: about 11 km | Statement: [Battle of Loos, frontlineLengthApprox, about 11 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontlineLengthApprox Context triple: [Battle of Loos, frontlineLengthApprox, about 11 km]
-
A.
frontLineLength
chosen
Indicates the total measured extent of the front line where opposing forces or boundaries directly face each other.
-
B.
frontLength
Indicates the length measurement of the front side or edge of an object relative to its overall dimensions.
-
C.
frontLine
Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
-
D.
frontLineStrength
Indicates the level of combat capability or effectiveness of forces positioned at the front line in a conflict or operation.
-
E.
frontLineBetween
Indicates that a boundary or line of direct confrontation exists separating two opposing sides or regions.
- 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_69ca84e7506c819095cbde4ff16512bb |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3d62628819094786a49b9bcd09b |
completed | April 2, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69cd1d7621d48190aa6a6f34399514b0 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:36 p.m.