Triple
T38128869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahabodhi Mahavihara |
E952159
|
entity |
| Predicate | sacredTreeType |
P136537
|
FINISHED |
| Object | Ficus religiosa |
—
|
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: Ficus religiosa | Statement: [Mahabodhi Mahavihara, sacredTreeType, Ficus religiosa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacredTreeType Context triple: [Mahabodhi Mahavihara, sacredTreeType, Ficus religiosa]
-
A.
sacredTree
Indicates that an entity is regarded as a sacred or holy tree within a religious, spiritual, or cultural context.
-
B.
associatedWithSacredTree
chosen
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.
hasSacredTreeAge
Indicates that an entity is associated with a sacred tree characterized by a specific age or age range.
-
D.
sacredElement
Indicates that one entity is regarded as holy, revered, or spiritually significant within the religious or cultural context of the other entity.
-
E.
commonTreeType
Indicates that two or more entities share the same type or classification of tree.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.