Triple
T5602119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeke |
E147143
|
entity |
| Predicate | referredAircraftEnteredService |
P64997
|
FINISHED |
| Object | 1940 |
—
|
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: 1940 | Statement: [Zeke, referredAircraftEnteredService, 1940]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referredAircraftEnteredService Context triple: [Zeke, referredAircraftEnteredService, 1940]
-
A.
firstServiceAircraft
Indicates that the subject aircraft is the first of its type to enter operational service with the specified operator or organization.
-
B.
takenIntoServiceAs
Indicates that one entity has been formally accepted, enrolled, or commissioned to perform service or duty for another entity.
-
C.
previousAircraftUsed
Indicates that one aircraft was used immediately before another in a sequence of aircraft usage.
-
D.
enteredUSAAFService
Indicates that an entity began active service in the United States Army Air Forces.
-
E.
successorAircraft
Indicates that one aircraft model directly follows and replaces another in a developmental or operational sequence.
- 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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020dbd6dc8190ba011876c205754e |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f4032408190a4f0d2eb21ebd870 |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:39 p.m.