Triple
T7768682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mackinac Island Airport |
E179013
|
entity |
| Predicate | serves as gateway for |
P10516
|
FINISHED |
| Object | tourists |
—
|
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: tourists | Statement: [Mackinac Island Airport, serves as gateway for, tourists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serves as gateway for Context triple: [Mackinac Island Airport, serves as gateway for, tourists]
-
A.
servesAsGatewayTo
chosen
Indicates that one entity functions as an entry point, access route, or intermediary channel that enables reaching or connecting to another entity.
-
B.
architectOfGateway
Indicates that one entity is the architect responsible for designing or creating a specific gateway associated with another entity.
-
C.
servesCircuit
Indicates that an entity provides legal representation or service in a specified judicial circuit.
-
D.
isMajorInternationalGatewayFor
Indicates that one entity serves as a primary, globally significant access point or hub for another entity’s international connections or flows.
-
E.
servesUnder
Indicates that one entity works in a subordinate role under the authority, command, or supervision of another entity.
- 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.