Triple
T9585702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hogwarts Great Hall (Harry Potter films) |
E231282
|
entity |
| Predicate | lightingIncludes |
P1280
|
FINISHED |
| Object | floating candles effect |
—
|
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: floating candles effect | Statement: [Hogwarts Great Hall (Harry Potter films), lightingIncludes, floating candles effect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightingIncludes Context triple: [Hogwarts Great Hall (Harry Potter films), lightingIncludes, floating candles effect]
-
A.
hasLighting
chosen
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
B.
lightType
Indicates the specific category or kind of light associated with an entity or lighting setup.
-
C.
lightingColor
Indicates the color or hue of the lighting applied to or associated with an entity.
-
D.
lightSourceFor
Indicates that one entity serves as the source of illumination for another entity.
-
E.
lightingDependsOn
Indicates that the state or behavior of lighting is determined or influenced by another specified factor or condition.
- 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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99edc2c08190b67b40f6214d46f1 |
completed | April 1, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:06 p.m.