Triple
T16225983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Knight |
E393844
|
entity |
| Predicate | indoorQueue |
P40792
|
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: [Dark Knight, indoorQueue, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indoorQueue Context triple: [Dark Knight, indoorQueue, true]
-
A.
hasTouristQueue
Indicates that there is a designated queue or waiting line specifically for tourists in relation to a place, service, or attraction.
-
B.
queueLocation
chosen
Indicates the place or position where an entity is arranged to wait in a queue or line.
-
C.
isNextInLineTo
Indicates that one entity is immediately scheduled or positioned to receive something or assume a role after another entity.
-
D.
indoorPopularity
Indicates how frequently or strongly something is favored, used, or visited in indoor settings.
-
E.
hasWaitingArea
Indicates that an entity provides or includes a designated space where people can wait before receiving a service or proceeding to another area.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d25f8bc81909aa59b794a528db2 |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.