Triple
T17401943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airbus A321neo |
E423110
|
entity |
| Predicate | entryIntoServiceYear |
P77922
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Airbus A321neo, entryIntoServiceYear, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryIntoServiceYear Context triple: [Airbus A321neo, entryIntoServiceYear, 2017]
-
A.
startServiceYear
chosen
Indicates the year in which an entity began providing a particular service or started its service-related activity.
-
B.
enteredServiceYearWithUSN
Indicates the year in which an entity (such as a vessel or asset) officially entered active service with the United States Navy.
-
C.
accessionYear
Indicates the calendar year in which an item, record, or entity was formally added to or registered within a collection, system, or institution.
-
D.
exitYear
Indicates the year in which an entity leaves, finishes, or ceases its association with another entity or context.
-
E.
enlistmentYear
Indicates the year in which an entity formally joined or was enrolled into a service, organization, or group.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43b046ad88190a95bbeda4e602514 |
completed | April 19, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.