Triple
T22209467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-8 Crusader |
E548901
|
entity |
| Predicate | retiredFromUSMCService |
P120201
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [F-8 Crusader, retiredFromUSMCService, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retiredFromUSMCService Context triple: [F-8 Crusader, retiredFromUSMCService, 1970s]
-
A.
retiredFromUSMilitary
Indicates that an individual previously served in the United States military and has formally ended their military career or service.
-
B.
retiredFromUSMCFrontlineService
chosen
Indicates that an individual has ended their active frontline duty service in the United States Marine Corps.
-
C.
retiredFromFrontlineService
Indicates that an entity has ceased active, primary operational duties and is no longer serving in a frontline role.
-
D.
retiredFromCanadianForces
Indicates that an individual has ended their service or career in the Canadian Armed Forces.
-
E.
hadMilitaryServiceFrom
Indicates that an entity performed or was engaged in military service starting from a specified point in time.
- 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.