Triple
T11329690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sesame Street Spaghetti Space Chase |
E268307
|
entity |
| Predicate | hasExpressQueue |
P24240
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sesame Street Spaghetti Space Chase, hasExpressQueue, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExpressQueue Context triple: [Sesame Street Spaghetti Space Chase, hasExpressQueue, true]
-
A.
hasQueue
Indicates that an entity maintains or is associated with a queue, typically representing an ordered list of items or tasks awaiting processing.
-
B.
usesQueue
Indicates that one entity employs or relies on a queue mechanism to manage or process items, tasks, or messages.
-
C.
hasExpressSegments
Indicates that a route, service, or path includes segments that are designated as express, skipping certain intermediate stops or steps.
-
D.
hasQueueType
chosen
Indicates that an entity is associated with a specific type or category of queue.
-
E.
hasExpressTracks
Indicates that a transportation route or facility includes tracks designated for express service, allowing faster travel with fewer stops than regular tracks.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e330008190b75490efde01dc59 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.