Triple
T1888353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal Tower |
E41811
|
entity |
| Predicate | usesLightingFor |
P33064
|
FINISHED |
| Object | commemorative color displays |
—
|
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: commemorative color displays | Statement: [Terminal Tower, usesLightingFor, commemorative color displays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLightingFor Context triple: [Terminal Tower, usesLightingFor, commemorative color displays]
-
A.
hasLighting
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
B.
lightingColor
Indicates the color or hue of the lighting applied to or associated with an entity.
-
C.
lightingCharacteristic
Indicates the specific qualities or properties of how something is lit, such as brightness, color, direction, or style of illumination.
-
D.
lightingDesigner
Indicates that an entity is responsible for planning, creating, or supervising the lighting design for a production, event, or environment.
-
E.
lightSourceFor
Indicates that one entity serves as the source of illumination for another entity.
- 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb12382b481908cd26b56f8558226 |
completed | March 7, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69abafe61bc48190ac9ead027df930e1 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb11bfd2c8190a805372589f73238 |
completed | March 7, 2026, 5:01 a.m. |
Created at: March 4, 2026, 7:34 p.m.