Triple
T19938868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronkhorstspruit |
E479248
|
entity |
| Predicate | NanHuaTempleInstanceOf |
P64892
|
FINISHED |
| Object | Buddhist temple |
—
|
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: Buddhist temple | Statement: [Bronkhorstspruit, NanHuaTempleInstanceOf, Buddhist temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NanHuaTempleInstanceOf Context triple: [Bronkhorstspruit, NanHuaTempleInstanceOf, Buddhist temple]
-
A.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
B.
hasTempleOf
chosen
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
C.
isNumberedTempleOf
Indicates that one entity is a specific, designated temple identified by a particular number within a series or system associated with another entity.
-
D.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
E.
hillTemple
Indicates a relationship where a temple is located on, associated with, or dedicated to a hill.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a190ac08190b9dc7955c9764a71 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.