Triple
T7989233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shelters for Roman Archaeological Site Chur |
E185758
|
entity |
| Predicate | lightingStrategy |
P1280
|
FINISHED |
| Object | diffused daylight |
—
|
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: diffused daylight | Statement: [Shelters for Roman Archaeological Site Chur, lightingStrategy, diffused daylight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightingStrategy Context triple: [Shelters for Roman Archaeological Site Chur, lightingStrategy, diffused daylight]
-
A.
hasLighting
chosen
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
B.
lightingColor
Indicates the color or hue of the lighting applied to or associated with an entity.
-
C.
lightingOrder
Indicates the sequence or priority in which lighting elements are activated, adjusted, or controlled relative to one another.
-
D.
usesLightingFor
Indicates that one entity employs or relies on a particular lighting setup, technology, or condition to achieve a purpose or perform an action.
-
E.
laterLighting
Indicates that one lighting event or condition occurs after another in time.
- 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_69ca829a2cfc819083d591d58ec04075 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c4f98808190879113ad4af9bb4d |
completed | March 31, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:16 p.m.