Triple
T8962041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airbus A330-200F |
E214028
|
entity |
| Predicate | entryIntoService |
P2339
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Airbus A330-200F, entryIntoService, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryIntoService Context triple: [Airbus A330-200F, entryIntoService, 2010]
-
A.
enteredService
chosen
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
B.
enteredServiceWithUnit
Indicates that an entity began its period of service or active duty while assigned to a specified unit.
-
C.
takenIntoServiceAs
Indicates that one entity has been formally accepted, enrolled, or commissioned to perform service or duty for another entity.
-
D.
enteredServiceAsReplacementFor
Indicates that one entity began its period of service specifically to take over the role or function previously performed by another entity.
-
E.
introducedToService
Indicates that one entity has presented or brought another entity into contact with a particular service for the first 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_69ca839cd6008190a1546a701a56710c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6749e5008190a01f42a2e772dd54 |
completed | April 1, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:01 p.m.