Triple
T14138498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nit del Foc |
E350359
|
entity |
| Predicate | hasLightingCondition |
P42109
|
FINISHED |
| Object | dark night sky |
—
|
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: dark night sky | Statement: [Nit del Foc, hasLightingCondition, dark night sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLightingCondition Context triple: [Nit del Foc, hasLightingCondition, dark night sky]
-
A.
hasLighting
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
B.
illuminationCondition
chosen
Indicates the lighting or brightness conditions under which an event, observation, or interaction takes place.
-
C.
hasLightingEffect
Indicates that one entity applies, produces, or is associated with a particular lighting effect on another entity or environment.
-
D.
lightingRequirement
Indicates the level or type of light that is needed for something to function, grow, or be used properly.
-
E.
hasLightingPolicy
Indicates that there is a defined policy or set of rules governing how lighting is used, managed, or controlled for the related entity.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6111a36081909beff35c88a56960 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:39 a.m.