Triple
T31755844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Gateway |
E810553
|
entity |
| Predicate | isSecondaryEntranceOf |
P172510
|
FINISHED |
| Object | EPCOT |
—
|
NE NERFINISHED |
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: EPCOT | Statement: [International Gateway, isSecondaryEntranceOf, EPCOT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSecondaryEntranceOf Context triple: [International Gateway, isSecondaryEntranceOf, EPCOT]
-
A.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
B.
isCentralGateOf
Indicates that one entity serves as the main or primary gate or entrance of another entity.
-
C.
exitsThrough
Indicates that an entity leaves or departs from a place, structure, or area by passing through a specified exit or passage.
-
D.
hasSeparateEntrances
Indicates that the related entities each have their own distinct entrance, rather than sharing a common one.
-
E.
isMainEntrance
Indicates that an entrance serves as the primary or principal access point to a place or building.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:29 p.m.