Triple
T3279958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Night Café |
E68847
|
entity |
| Predicate | depictsLighting |
P1280
|
FINISHED |
| Object | gas‑lit interior |
—
|
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: gas‑lit interior | Statement: [The Night Café, depictsLighting, gas‑lit interior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsLighting Context triple: [The Night Café, depictsLighting, gas‑lit interior]
-
A.
hasLighting
chosen
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
B.
lightingCharacteristic
Indicates the specific qualities or properties of how something is lit, such as brightness, color, direction, or style of illumination.
-
C.
lightingDesigner
Indicates that an entity is responsible for planning, creating, or supervising the lighting design for a production, event, or environment.
-
D.
lightingColor
Indicates the color or hue of the lighting applied to or associated with an entity.
-
E.
usesLightingFor
Indicates that one entity employs or relies on a particular lighting setup, technology, or condition to achieve a purpose or perform an action.
- 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0166c8c81909cb0a580ef319be3 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.