Triple
T1915121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Powell Street terminal |
E39998
|
entity |
| Predicate | hasQueue |
P33920
|
FINISHED |
| Object | long passenger lines during peak tourist season |
—
|
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: long passenger lines during peak tourist season | Statement: [Powell Street terminal, hasQueue, long passenger lines during peak tourist season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQueue Context triple: [Powell Street terminal, hasQueue, long passenger lines during peak tourist season]
-
A.
hasQueueType
Indicates that an entity is associated with a specific type or category of queue.
-
B.
hasWaitingArea
Indicates that an entity provides or includes a designated space where people can wait before receiving a service or proceeding to another area.
-
C.
instructionQueueLength
Indicates the current number of instructions waiting in a queue to be processed.
-
D.
isNextInLineTo
Indicates that one entity is immediately scheduled or positioned to receive something or assume a role after another entity.
-
E.
hasPool
Indicates that one entity possesses, includes, or is equipped with a swimming pool.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafeba3d88190afcce67483d8625b |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb34c4a64819096e12b152b84c334 |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:35 p.m.