Triple
T29590200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPC |
E754132
|
entity |
| Predicate | hasIataLikeRole |
P167982
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [SPC, hasIataLikeRole, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIataLikeRole Context triple: [SPC, hasIataLikeRole, no]
-
A.
hasIATAFunction
Indicates that an entity has a specific role, status, or function as defined by the International Air Transport Association (IATA).
-
B.
hasIATAStyle
Indicates that one entity uses or conforms to the IATA (International Air Transport Association) style or formatting standard associated with another entity.
-
C.
hasIATAcode
Indicates that an entity, typically a transportation facility like an airport, is associated with a specific IATA (International Air Transport Association) code.
-
D.
associatedWithIATATypeCode
Indicates that one entity is linked to or characterized by a specific IATA type code that classifies its role or function in air transport.
-
E.
hasIATAFlightNumber
Indicates that an entity (typically a flight) is associated with a specific IATA-designated flight number.
- 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66e5f7e30819094530abceabd5f43 |
completed | May 2, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66d75a8788190aa9ca2c977429045 |
completed | May 2, 2026, 9:32 p.m. |
Created at: April 28, 2026, 6:13 p.m.