Triple
T20499459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ekambareswarar Temple |
E503261
|
entity |
| Predicate | hasSacredTreeSpecies |
P75235
|
FINISHED |
| Object | mango |
—
|
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: mango | Statement: [Ekambareswarar Temple, hasSacredTreeSpecies, mango]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredTreeSpecies Context triple: [Ekambareswarar Temple, hasSacredTreeSpecies, mango]
-
A.
sacredTree
Indicates that an entity is regarded as a sacred or holy tree within a religious, spiritual, or cultural context.
-
B.
associatedWithSacredTree
Indicates a relationship in which an entity is linked or connected to a sacred tree, such as by location, significance, use, or ritual association.
-
C.
hasTrees
Indicates that something possesses or contains one or more trees.
-
D.
hasTempleTree
chosen
Indicates that a location or entity possesses or contains a temple-associated tree.
-
E.
hasSacredNaturalFeature
Indicates that an entity possesses or is associated with a natural feature (such as a mountain, river, or grove) that is regarded as sacred.
- 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cc10cd08190915b6c29c6473f77 |
completed | April 20, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:35 a.m.