Triple
T5052571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fountains of Bellagio |
E113820
|
entity |
| Predicate | nightShowFeature |
P30895
|
FINISHED |
| Object | enhanced lighting effects |
—
|
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: enhanced lighting effects | Statement: [Fountains of Bellagio, nightShowFeature, enhanced lighting effects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nightShowFeature Context triple: [Fountains of Bellagio, nightShowFeature, enhanced lighting effects]
-
A.
featuresNighttimeShow
chosen
Indicates that an entity offers or includes a show or performance that takes place at night.
-
B.
livePerformanceFeature
Indicates that one entity is included or highlighted as a component of another entity’s live performance.
-
C.
prominentAtNight
Indicates that an entity becomes especially noticeable, visible, or significant during nighttime conditions.
-
D.
notableBroadcastFeature
Indicates that something has a distinctive or noteworthy characteristic related to its broadcast or transmission.
-
E.
specialFeature
Indicates that an entity possesses a distinctive or noteworthy attribute, capability, or characteristic that sets it apart from others.
- 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7428d7a88190b990aedae390acbe |
completed | March 20, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.