Triple
T17755513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dieng Plateau temples |
E443224
|
entity |
| Predicate | originalNumberOfTemples |
P43478
|
FINISHED |
| Object | larger than the number surviving today |
—
|
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: larger than the number surviving today | Statement: [Dieng Plateau temples, originalNumberOfTemples, larger than the number surviving today]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalNumberOfTemples Context triple: [Dieng Plateau temples, originalNumberOfTemples, larger than the number surviving today]
-
A.
pilgrimageTempleCount
Indicates the number of temples associated with or visited during a particular pilgrimage.
-
B.
hasTempleCount
chosen
Indicates that an entity is associated with a specified number of temples.
-
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.
foundedTemple
Indicates that an entity established or created a temple, typically as its founder.
-
E.
numberOfShrines
Indicates the total count of shrines associated with a given entity or context.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4841e7050819083a4e638ca7484f7 |
completed | April 19, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:10 a.m.