Triple
T22365940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CYYC |
E552903
|
entity |
| Predicate | hasRelatedIdentifierType |
P100200
|
FINISHED |
| Object | IATA airport code |
—
|
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: IATA airport code | Statement: [CYYC, hasRelatedIdentifierType, IATA airport code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatedIdentifierType Context triple: [CYYC, hasRelatedIdentifierType, IATA airport code]
-
A.
relatedIdentifier
Indicates that one identifier is associated with another identifier that refers to the same or a related entity in a different context or system.
-
B.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
C.
hasDigitalObjectIdentifier
Indicates that an entity is associated with a specific Digital Object Identifier (DOI) that uniquely identifies it in a digital environment.
-
D.
supportsIdentifierType
chosen
Indicates that one entity is capable of recognizing, handling, or working with a specified type or format of identifier.
-
E.
hasAssociatedType
Indicates that one entity is linked to another entity that specifies its type, category, or classification.
- 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1580074dc819091305ac7017000d3 |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.