Triple
T25693658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhumija |
E644260
|
entity |
| Predicate | towerOrganization |
P138763
|
FINISHED |
| Object | divided into vertical rathas (projections) carrying miniature spires |
—
|
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: divided into vertical rathas (projections) carrying miniature spires | Statement: [Bhumija, towerOrganization, divided into vertical rathas (projections) carrying miniature spires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: towerOrganization Context triple: [Bhumija, towerOrganization, divided into vertical rathas (projections) carrying miniature spires]
-
A.
towerFunction
Indicates that one entity serves as a tower-like structure or performs the function of a tower in relation to another entity.
-
B.
towerName
Indicates the specific name assigned to a tower in the relationship.
-
C.
towerArrangement
chosen
Indicates how towers are positioned or organized relative to one another within a given structure or layout.
-
D.
towerType
Indicates the specific kind or classification of a tower that an entity is associated with or represents.
-
E.
towerLocation
Indicates that a tower is located at, or associated with, a specific place or geographic location.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fbc2bcbc81909e16230a8ed01210 |
completed | May 2, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 8:32 p.m.