Triple
T22209494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-8 Crusader |
E548901
|
entity |
| Predicate | combatRoleInVietnamWar |
P108011
|
FINISHED |
| Object | fighter escort |
—
|
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: fighter escort | Statement: [F-8 Crusader, combatRoleInVietnamWar, fighter escort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatRoleInVietnamWar Context triple: [F-8 Crusader, combatRoleInVietnamWar, fighter escort]
-
A.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
higherCommandDuringVietnamWar
Indicates that one entity served in a higher-level command role over another entity during the Vietnam War.
-
C.
positionOnVietnamWar
Indicates a person or entity’s stance, opinion, or policy position regarding the Vietnam War.
-
D.
formerMilitaryRole
Indicates that an entity previously held, but no longer holds, a specific military role or position.
-
E.
roleInWarOrConflict
chosen
Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
- 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_69e11e3f7e04819089806d81d5ac431e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b2aefb881909bddbabd4be0bd58 |
completed | April 28, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:36 p.m.