Triple
T13168772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Place Stanislas |
E312919
|
entity |
| Predicate | hasLightingShow |
P31011
|
FINISHED |
| Object | summer light and sound show |
—
|
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: summer light and sound show | Statement: [Place Stanislas, hasLightingShow, summer light and sound show]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLightingShow Context triple: [Place Stanislas, hasLightingShow, summer light and sound show]
-
A.
hasLightShow
chosen
Indicates that an entity features or presents a light-based visual display or performance.
-
B.
hasLaserShow
Indicates that an entity features or offers a laser-based visual show as part of its activities or attractions.
-
C.
hasLighting
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
D.
hasLightingRitualTime
Indicates the specific time at which a lighting-related ritual or ceremony is performed.
-
E.
lightingEvents
Indicates events or actions involving the activation, change, or control of lighting.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:13 p.m.