Triple
T27158925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peruvudaiyar Kovil |
E682602
|
entity |
| Predicate | hasVimanaHeight |
P169559
|
FINISHED |
| Object | about 60 meters |
—
|
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: about 60 meters | Statement: [Peruvudaiyar Kovil, hasVimanaHeight, about 60 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVimanaHeight Context triple: [Peruvudaiyar Kovil, hasVimanaHeight, about 60 meters]
-
A.
hasVimana
Indicates that an entity possesses, is associated with, or makes use of a vimana (a flying craft or aerial vehicle).
-
B.
hasPylonHeight
Indicates that an entity is associated with a specific height value of a pylon.
-
C.
naveHeight
Indicates the vertical distance from the floor to the highest point of the nave space in a building.
-
D.
hasCentralPylonHeight
Indicates the height measurement of the central pylon in a structure or system.
-
E.
hasTowerHeight
Indicates that an entity (such as a tower or structure) has a specific height value associated with it.
- F. None of above. chosen
Provenance (4 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f67fc237608190b6542b56038a7fe4 |
completed | May 2, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f0353c88190a05b2db449abe0f4 |
completed | May 2, 2026, 10:47 p.m. |
Created at: April 27, 2026, 9:17 a.m.