Triple
T26116413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etihad Guest Miles |
E658834
|
entity |
| Predicate | associatedWithProgramLaunchYear |
P197897
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [Etihad Guest Miles, associatedWithProgramLaunchYear, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithProgramLaunchYear Context triple: [Etihad Guest Miles, associatedWithProgramLaunchYear, 2006]
-
A.
associatedWithInductionYear
Indicates that an entity is linked to a specific year in which an induction (such as into a group, hall of fame, or organization) took place.
-
B.
associatedClassYear
Indicates a relationship linking an entity to the specific academic class year with which it is connected or identified.
-
C.
associatedWithAcademicProgram
Indicates that an entity has a formal connection or linkage to a specific academic program.
-
D.
establishedForProgram
Indicates that something has been created or set up specifically to support, serve, or be used by a particular program.
-
E.
applicationYear
Indicates the year in which an application was submitted or made.
- 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_69ee5bc20298819099a42be042eb2349 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
| PDg | Predicate description generation | batch_69feb8e6ed7881908446745c89c30784 |
completed | May 9, 2026, 4:32 a.m. |
Created at: April 26, 2026, 8:05 p.m.