Triple
T10890351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheffield Avenue bar district |
E257156
|
entity |
| Predicate | openLate |
P96253
|
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: [Sheffield Avenue bar district, openLate, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openLate Context triple: [Sheffield Avenue bar district, openLate, true]
-
A.
opened
Indicates that one entity caused another entity (such as an object, container, or passage) to change from a closed or inaccessible state to an open or accessible state.
-
B.
endedDueTo
Indicates that an event, process, or state came to a conclusion specifically because of a particular cause or condition.
-
C.
openedAt
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
-
D.
opens
Indicates that one entity causes or allows another entity (such as an object, space, or resource) to become accessible or no longer closed.
-
E.
openedBetween
Indicates that an entity was opened during a time interval that falls between two specified temporal bounds.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d752041e2c8190b513dc9dc5857fcc |
completed | April 9, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101de31c819090707635f6790559 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:21 p.m.