Triple
T8856496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koodal Azhagar Temple |
E210769
|
entity |
| Predicate | hasTowerOrientation |
P12663
|
FINISHED |
| Object | east-facing gopuram |
—
|
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: east-facing gopuram | Statement: [Koodal Azhagar Temple, hasTowerOrientation, east-facing gopuram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTowerOrientation Context triple: [Koodal Azhagar Temple, hasTowerOrientation, east-facing gopuram]
-
A.
hasTowerPosition
Indicates that an entity occupies or is assigned a specific position or location within a tower.
-
B.
hasTower
Indicates that one entity possesses, contains, or is characterized by the presence of a tower.
-
C.
hasTowerHeight
Indicates that an entity (such as a tower or structure) has a specific height value associated with it.
-
D.
hasOrientation
chosen
Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
-
E.
isObservationTower
Indicates that something functions as an observation tower, serving primarily as a structure for viewing or monitoring an area from an elevated position.
- 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60e259248190abd334bbfcdcb955 |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:50 p.m.