Triple
T769668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadway |
E16252
|
entity |
| Predicate | hasLightingFeature |
P1280
|
FINISHED |
| Object | bright theater marquees |
—
|
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: bright theater marquees | Statement: [Broadway, hasLightingFeature, bright theater marquees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLightingFeature Context triple: [Broadway, hasLightingFeature, bright theater marquees]
-
A.
hasLighting
chosen
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
B.
hasTorchRelay
Indicates that an event or entity includes or is associated with a torch relay as part of its activities or proceedings.
-
C.
hasRunwayLighting
Indicates that a runway is equipped with lighting systems to aid visibility and operations, typically during low-light or night conditions.
-
D.
hasBacklitKeyboard
Indicates that an entity is equipped with a keyboard that includes built-in lighting behind the keys.
-
E.
lightSourceFor
Indicates that one entity serves as the source of illumination for another entity.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a70376988190be2826259f5281ab |
completed | March 1, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69a4a508c42c8190850a0ac7844a3ea9 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.