Triple
T26586872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jatinga |
E667232
|
entity |
| Predicate | explanationsProposedForPhenomenon |
P3638
|
FINISHED |
| Object | attraction to village lights |
—
|
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: attraction to village lights | Statement: [Jatinga, explanationsProposedForPhenomenon, attraction to village lights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explanationsProposedForPhenomenon Context triple: [Jatinga, explanationsProposedForPhenomenon, attraction to village lights]
-
A.
examplePhenomenon
Indicates a representative or illustrative occurrence used to demonstrate or clarify a broader phenomenon or pattern.
-
B.
encounteredPhenomenon
Indicates that an entity has come across, experienced, or observed a particular phenomenon.
-
C.
allegedPhenomenon
Indicates that something is claimed or reported to be a phenomenon, but its existence, cause, or nature is uncertain or disputed.
-
D.
affectsPhenomenon
Indicates that one phenomenon produces an influence or change on another phenomenon.
-
E.
usedToExplain
chosen
Indicates that one entity serves as an explanation or clarification for another 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 2:06 a.m.