Triple
T26541770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thud |
E671406
|
entity |
| Predicate | withdrawnFromFrontlineUSAFService |
P35163
|
FINISHED |
| Object | early 1980s |
—
|
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: early 1980s | Statement: [Thud, withdrawnFromFrontlineUSAFService, early 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withdrawnFromFrontlineUSAFService Context triple: [Thud, withdrawnFromFrontlineUSAFService, early 1980s]
-
A.
retiredFromUSMCFrontlineService
Indicates that an individual has ended their active frontline duty service in the United States Marine Corps.
-
B.
retiredFromFrontlineService
chosen
Indicates that an entity has ceased active, primary operational duties and is no longer serving in a frontline role.
-
C.
retiredFromUSMilitary
Indicates that an individual previously served in the United States military and has formally ended their military career or service.
-
D.
retiredFromRAAFService
Indicates that an individual has ended or concluded their period of service in the Royal Australian Air Force.
-
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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61431eb008190affb2b34864b3e8a |
completed | May 2, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:42 a.m.