Triple
T18836875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kandariya Mahadeva Temple |
E460686
|
entity |
| Predicate | hasEntranceHall |
P121628
|
FINISHED |
| Object | ardha-mandapa |
—
|
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: ardha-mandapa | Statement: [Kandariya Mahadeva Temple, hasEntranceHall, ardha-mandapa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEntranceHall Context triple: [Kandariya Mahadeva Temple, hasEntranceHall, ardha-mandapa]
-
A.
hasMainHall
Indicates that an entity possesses or includes a primary or central hall as a significant internal space.
-
B.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
C.
hasReceptionHall
chosen
Indicates that one entity possesses or includes a reception hall as part of its facilities or structure.
-
D.
hasMainHallType
Indicates the specific category or kind of main hall associated with an entity.
-
E.
hasEntranceStructure
Indicates that one entity possesses or is associated with a specific physical structure that serves as its entrance.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99e86388190957acaaab401b5cb |
completed | April 20, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.