Triple
T12242577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rikugien Garden |
E291769
|
entity |
| Predicate | lightingEvents |
P103982
|
FINISHED |
| Object | held in spring and autumn |
—
|
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: held in spring and autumn | Statement: [Rikugien Garden, lightingEvents, held in spring and autumn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightingEvents Context triple: [Rikugien Garden, lightingEvents, held in spring and autumn]
-
A.
lightingColorChangesForEvents
Indicates that the color of lighting is altered in response to specific events or event conditions.
-
B.
lightingPractice
Indicates a relationship where an entity engages in or performs activities to rehearse, refine, or experiment with lighting setups or techniques.
-
C.
hasLighting
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
D.
lightingAttendedBy
Indicates that a lighting-related event, activity, or installation is attended or participated in by a specified entity.
-
E.
laterLightSource
Indicates that one light source occurs or is activated after another in time.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d924a3973c8190a882046963b320fb |
completed | April 10, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69d91c41bcbc81909782f4e3c571b218 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d92468052c819090546f36d009a64f |
completed | April 10, 2026, 4:25 p.m. |
Created at: April 8, 2026, 9:51 p.m.