Triple
T6961487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thin Red Line |
E161378
|
entity |
| Predicate | frontFormation |
P49150
|
FINISHED |
| Object | two-deep line |
—
|
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: two-deep line | Statement: [Thin Red Line, frontFormation, two-deep line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontFormation Context triple: [Thin Red Line, frontFormation, two-deep line]
-
A.
bandFormation
Indicates the event or process by which a musical band is created or comes together as a group.
-
B.
militaryFormationOf
Indicates that one entity is a military unit or formation that is organizationally part of, or derived from, another entity.
-
C.
commandedFormation
Indicates that one entity held command authority over a specific military or organizational formation.
-
D.
tacticalFormation
chosen
Indicates a specific strategic arrangement or positioning of entities relative to one another to achieve a tactical objective.
-
E.
frontLine
Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
- 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6daf07e3481909aa79b8e0f1b1be7 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:30 p.m.