Triple
T15405323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christmas Tree Lane |
E368436
|
entity |
| Predicate | lightingTraditionStartYear |
P81080
|
FINISHED |
| Object | 1920 |
—
|
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: 1920 | Statement: [Christmas Tree Lane, lightingTraditionStartYear, 1920]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightingTraditionStartYear Context triple: [Christmas Tree Lane, lightingTraditionStartYear, 1920]
-
A.
firstLightingYear
chosen
Indicates the year in which something (such as a light source or lighting installation) was first put into operation or illuminated.
-
B.
traditionallyLitAt
Indicates that something is customarily illuminated by something else according to tradition or established practice.
-
C.
lightingTime
Indicates the time at which a lighting event or illumination occurs or is scheduled.
-
D.
heritageRevelationYear
Indicates the year in which a particular heritage status, designation, or significance was formally revealed, recognized, or made public.
-
E.
lightingEvents
Indicates events or actions involving the activation, change, or control of lighting.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e8fde64819082ec0c68df305561 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.