Triple
T17754071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia Carousel |
E443185
|
entity |
| Predicate | hasQueueLocation |
P40792
|
FINISHED |
| Object | park entrance plaza |
—
|
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: park entrance plaza | Statement: [Columbia Carousel, hasQueueLocation, park entrance plaza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQueueLocation Context triple: [Columbia Carousel, hasQueueLocation, park entrance plaza]
-
A.
queueLocation
chosen
Indicates the place or position where an entity is arranged to wait in a queue or line.
-
B.
hasQueue
Indicates that an entity maintains or is associated with a queue, typically representing an ordered list of items or tasks awaiting processing.
-
C.
hasQueueAccessibility
Indicates that an entity provides accessible features or accommodations for people with disabilities in its queuing or waiting areas.
-
D.
hasReceiverLocation
Indicates that an entity serves as the destination or location where something is received by another party.
-
E.
hasStageLocation
Indicates that an event, process, or staged activity occurs at or is associated with a specific location.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4841da9988190b5efde3bbd3f24c3 |
completed | April 19, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:10 a.m.