Triple
T26579700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomorrowland Transit Authority PeopleMover |
E667043
|
entity |
| Predicate | boardingStyle |
P162345
|
FINISHED |
| Object | Moving walkway loading platform |
—
|
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: Moving walkway loading platform | Statement: [Tomorrowland Transit Authority PeopleMover, boardingStyle, Moving walkway loading platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardingStyle Context triple: [Tomorrowland Transit Authority PeopleMover, boardingStyle, Moving walkway loading platform]
-
A.
structureStyle
Indicates the architectural or design style characterizing how a structure is built or formed.
-
B.
positionStyle
Indicates how an entity is positioned or arranged relative to a reference frame, layout, or context.
-
C.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
D.
bindingStyle
Indicates the method or format by which two components, systems, or interfaces are connected or integrated for interaction.
-
E.
strapStyle
Indicates the type or design of strap used on or associated with an item.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6250321088190ae3ed1dc9f2fcd03 |
completed | May 2, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f62473a38481909b919f88ffb5b492 |
completed | May 2, 2026, 4:21 p.m. |
Created at: April 27, 2026, 2:02 a.m.