Triple
T18116090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Candi Sewu |
E433607
|
entity |
| Predicate | hasMainTempleType |
P8490
|
FINISHED |
| Object | central main shrine |
—
|
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: central main shrine | Statement: [Candi Sewu, hasMainTempleType, central main shrine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainTempleType Context triple: [Candi Sewu, hasMainTempleType, central main shrine]
-
A.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
B.
hasMainAltarFor
Indicates that a specific altar serves as the primary or central altar designated for a particular entity, such as a church, chapel, or religious space.
-
C.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
D.
mainTemple
chosen
Indicates that one entity serves as the primary or central temple associated with another entity.
-
E.
hasMajorShrine
Indicates that one entity serves as a principal or primary shrine dedicated to 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd58ea8819081e2bec5e591e093 |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.