Triple
T34393530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HSBC Rain Vortex |
E882769
|
entity |
| Predicate | lightShow |
P31011
|
FINISHED |
| Object | nightly 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: nightly light and sound show | Statement: [HSBC Rain Vortex, lightShow, nightly light and sound show]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightShow Context triple: [HSBC Rain Vortex, lightShow, nightly light and sound show]
-
A.
hasLightShow
chosen
Indicates that an entity features or presents a light-based visual display or performance.
-
B.
lightOrganFunction
Indicates that one entity serves as the functional light-producing organ or structure for another entity.
-
C.
lightFunction
Indicates that one entity serves as a source or means of illumination or lighting for another entity or context.
-
D.
lightType
Indicates the specific category or kind of light associated with an entity or lighting setup.
-
E.
lightName
Indicates the designated name or label assigned to a specific light or lighting element.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.