Triple
T37395829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruby Red Icicle Chandelier |
E928849
|
entity |
| Predicate | lightingFunction |
P188028
|
FINISHED |
| Object | chandelier |
—
|
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: chandelier | Statement: [Ruby Red Icicle Chandelier, lightingFunction, chandelier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightingFunction Context triple: [Ruby Red Icicle Chandelier, lightingFunction, chandelier]
-
A.
lightFunction
Indicates that one entity serves as a source or means of illumination or lighting for another entity or context.
-
B.
lightingProvider
Indicates that one entity serves as the source or supplier of lighting for another entity or context.
-
C.
lightingColor
Indicates the color or hue of the lighting applied to or associated with an entity.
-
D.
hasLighting
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
E.
lightingDependsOn
Indicates that the state or behavior of lighting is determined or influenced by another specified factor or condition.
- 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb9e173f348190b7ab5935e4dca039 |
completed | May 6, 2026, 8:01 p.m. |
Created at: May 3, 2026, 4:16 p.m.