Triple
T35075956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arco lamp |
E1012308
|
entity |
| Predicate | lightSourcePosition |
P182079
|
FINISHED |
| Object | suspended over seating or table area |
—
|
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: suspended over seating or table area | Statement: [Arco lamp, lightSourcePosition, suspended over seating or table area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightSourcePosition Context triple: [Arco lamp, lightSourcePosition, suspended over seating or table area]
-
A.
lightSourceFor
Indicates that one entity serves as the source of illumination for another entity.
-
B.
laterLightSource
Indicates that one light source occurs or is activated after another in time.
-
C.
lightOrganLocation
Indicates the anatomical location or placement of a light-producing organ within or on an organism.
-
D.
torchLightingLocation
Indicates the location where a torch is or should be lit in relation to another entity or environment.
-
E.
lightFirstLit
Indicates that this light is the first one to be turned on or become illuminated in a given sequence or context.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865b4684819093f95e659522b75e |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.