Triple
T26224481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Narasimha Deva I |
E655850
|
entity |
| Predicate | monumentalWork |
P25270
|
FINISHED |
| Object | temple constructions in Odisha |
—
|
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: temple constructions in Odisha | Statement: [Narasimha Deva I, monumentalWork, temple constructions in Odisha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monumentalWork Context triple: [Narasimha Deva I, monumentalWork, temple constructions in Odisha]
-
A.
builtMonument
chosen
Indicates that one entity constructed or created a monument in honor of, or related to, another entity.
-
B.
memorialWork
Indicates that one entity is a commemorative work (such as a monument, plaque, or artwork) created to honor or remember another entity.
-
C.
monumentType
Indicates the specific kind or category of monument that an entity is classified as.
-
D.
significantMonument
Indicates that something is a monument of notable historical, cultural, or symbolic importance.
-
E.
otherMonuments
Indicates that there exists a relationship between an entity and additional monuments that are associated with or related to it in some relevant way.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d52254c8190baece694af79ff3a |
completed | May 2, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 8:57 p.m.