Triple
T11835834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian Christmas Tree (Edinburgh) |
E281512
|
entity |
| Predicate | lightingAttendedBy |
P101763
|
FINISHED |
| Object | local officials |
—
|
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: local officials | Statement: [Norwegian Christmas Tree (Edinburgh), lightingAttendedBy, local officials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightingAttendedBy Context triple: [Norwegian Christmas Tree (Edinburgh), lightingAttendedBy, local officials]
-
A.
roleAtIllumination
Indicates that an entity holds or held a specific role or position at the organization Illumination.
-
B.
hasLighting
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
C.
hasLightShow
Indicates that an entity features or presents a light-based visual display or performance.
-
D.
laterAttends
Indicates that one entity attends an event or place at a time later than another referenced attendance.
-
E.
lightingControlledBy
Indicates that the lighting system or device is operated, regulated, or influenced by a specified controller or control mechanism.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a62fec0881908c7b89c0b5bcc9a2 |
completed | April 10, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.