Triple
T22169657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batu Cermin Cave |
E547884
|
entity |
| Predicate | lightEffectCause |
P69537
|
FINISHED |
| Object | sunlight reflecting off cave walls |
—
|
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: sunlight reflecting off cave walls | Statement: [Batu Cermin Cave, lightEffectCause, sunlight reflecting off cave walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightEffectCause Context triple: [Batu Cermin Cave, lightEffectCause, sunlight reflecting off cave walls]
-
A.
lightFunction
Indicates that one entity serves as a source or means of illumination or lighting for another entity or context.
-
B.
lightOrganFunction
Indicates that one entity serves as the functional light-producing organ or structure for another entity.
-
C.
lightType
Indicates the specific category or kind of light associated with an entity or lighting setup.
-
D.
hasLightingEffect
chosen
Indicates that one entity applies, produces, or is associated with a particular lighting effect on another entity or environment.
-
E.
lightRange
Indicates the distance or area over which a light source effectively emits or illuminates.
- 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_69e11e3c4c5c81908d336165816b12e0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a6721e8819081d732df2691f4a4 |
completed | April 28, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.