Triple
T7768695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mackinac Island Airport |
E179013
|
entity |
| Predicate | has code type |
P56964
|
FINISHED |
| Object | IATA |
—
|
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 | Statement: [Mackinac Island Airport, has code type, IATA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has code type Context triple: [Mackinac Island Airport, has code type, IATA]
-
A.
hasTypeCode
chosen
Indicates that an entity is associated with a specific type classification represented by a code.
-
B.
codeType
Indicates the classification or category assigned to a particular code within a coding or encoding system.
-
C.
hasCommunicationCodeType
Indicates that an entity is associated with a specific type or category of communication code (e.g., phone, fax, email, messaging).
-
D.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of another entity.
-
E.
hasProgramCode
Indicates that an entity is associated with a specific program identifier or code used to reference or classify it within a system.
- 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_69c69f30602c819082ab52cd4af5c592 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c704376dc08190890f5ebb9f259cfd |
completed | March 27, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69c7016f4ce881909c2e9f610255187b |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:11 p.m.