Triple
T2423436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American F-100 Super Sabre |
E53470
|
entity |
| Predicate | enteredUSAFService |
P19194
|
FINISHED |
| Object | 1954 |
—
|
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: 1954 | Statement: [North American F-100 Super Sabre, enteredUSAFService, 1954]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredUSAFService Context triple: [North American F-100 Super Sabre, enteredUSAFService, 1954]
-
A.
enlistedIn
Indicates that an individual has formally joined and is serving in a particular military or service organization.
-
B.
placeOfMilitaryService
Indicates the location or institution where a person performed their military service.
-
C.
hasMilitaryBranch
Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
-
D.
militaryBranchEligibility
Indicates that an entity meets the required conditions to serve in a specified branch of the military.
-
E.
hasMilitaryServiceStart
chosen
Indicates the date or point in time when an entity’s period of military service began.
- 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_69ab495c44d48190b7235b23719bc3f6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc9f342e88190a430b02842ded418 |
completed | March 7, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69abc5a889948190b77de4ef6ac815a8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:42 p.m.