Triple
T26116382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etihad Guest Miles |
E658834
|
entity |
| Predicate | accruedFrom |
P97196
|
FINISHED |
| Object | Etihad Airways flights |
—
|
NE NERFINISHED |
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: Etihad Airways flights | Statement: [Etihad Guest Miles, accruedFrom, Etihad Airways flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accruedFrom Context triple: [Etihad Guest Miles, accruedFrom, Etihad Airways flights]
-
A.
accrualFrom
chosen
Indicates that something (such as a benefit, cost, or amount) arises, accumulates, or is derived from a specified source or cause.
-
B.
accrualUnit
Indicates the unit of measure (such as days, months, or years) in which something accumulates or is accrued over time.
-
C.
accrualMethod
Indicates the method or basis by which something (such as interest, revenue, or benefits) is accumulated or recognized over time.
-
D.
accretedBy
Indicates that one entity has grown or increased in mass or size through the gradual accumulation or absorption of another entity.
-
E.
chargeDate
Indicates the date on which a financial charge or billing action is applied or recorded.
- 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_69ee5bc20298819099a42be042eb2349 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60ac86d908190bf582de7891fb4b3 |
completed | May 2, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:05 p.m.