Triple
T26012215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suamox |
E646930
|
entity |
| Predicate | hadMajorTemple |
P8490
|
FINISHED |
| Object | Sun Temple of Suamox |
—
|
NE NERFINISHED |
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: Sun Temple of Suamox | Statement: [Suamox, hadMajorTemple, Sun Temple of Suamox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMajorTemple Context triple: [Suamox, hadMajorTemple, Sun Temple of Suamox]
-
A.
hadTempleDedicatedTo
Indicates that a temple was formally dedicated in honor of, or for the worship of, a particular entity.
-
B.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
C.
hasMajorShrine
Indicates that one entity serves as a principal or primary shrine dedicated to another entity.
-
D.
mainTemple
chosen
Indicates that one entity serves as the primary or central temple associated with another entity.
-
E.
hasHistoricTemple
Indicates that an entity possesses, contains, or is associated with a temple of historical significance.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605b5f34c8190880875cdd32ab051 |
completed | May 2, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:02 a.m.