Triple
T25104667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Airport Awards |
E628833
|
entity |
| Predicate | targetRespondents |
P36376
|
FINISHED |
| Object | airline passengers |
—
|
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: airline passengers | Statement: [World Airport Awards, targetRespondents, airline passengers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetRespondents Context triple: [World Airport Awards, targetRespondents, airline passengers]
-
A.
surveyParticipants
chosen
Indicates that certain entities take part in or respond to a survey.
-
B.
targetsGroup
Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
-
C.
targetConstituents
Indicates that a larger entity is directed toward, affects, or is specifically intended for certain constituent parts or members within a whole.
-
D.
estimatedInformants
Indicates that one entity has made an approximate or inferred determination of the number or identity of informants associated with another entity or situation.
-
E.
targetStudentsFrom
Indicates that an entity directs its efforts, services, or offerings specifically toward a defined group of students.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 6:26 a.m.