Triple
T23719774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockheed F-104 Starfighter |
E586107
|
entity |
| Predicate | enteredNATOService |
P153688
|
FINISHED |
| Object | late 1950s |
—
|
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: late 1950s | Statement: [Lockheed F-104 Starfighter, enteredNATOService, late 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredNATOService Context triple: [Lockheed F-104 Starfighter, enteredNATOService, late 1950s]
-
A.
enteredUSAAFService
Indicates that an entity began active service in the United States Army Air Forces.
-
B.
musteredIntoService
Indicates that an entity has been formally enrolled or assembled into active duty or official service under an authority.
-
C.
enteredRoyalNavyFrontlineService
Indicates that an entity began active duty or operational deployment in the frontline forces of the Royal Navy.
-
D.
enlistedIn
Indicates that an individual has formally joined and is serving in a particular military or service organization.
-
E.
placeOfMilitaryService
Indicates the location or institution where a person performed their military service.
- F. None of above. chosen
Provenance (4 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b77e2dc081908aef7a4c9b188dbd |
completed | April 29, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15b453da88190889a8d9b21727958 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 17, 2026, 7 p.m.