Triple
T26980311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brihadeeswara |
E679583
|
entity |
| Predicate | hasTempleOrientation |
P111924
|
FINISHED |
| Object | east-facing |
—
|
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 | Statement: [Brihadeeswara, hasTempleOrientation, east-facing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTempleOrientation Context triple: [Brihadeeswara, hasTempleOrientation, east-facing]
-
A.
hasGoddessShrineOrientation
Indicates the directional orientation or alignment of a shrine dedicated to a goddess in relation to a reference point or axis.
-
B.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
C.
mainShrineOrientation
chosen
Indicates the directional alignment or facing direction of a main shrine relative to a reference point or axis.
-
D.
hasTempleFeature
Indicates that an entity possesses a specific architectural or structural feature characteristic of a temple.
-
E.
hasTempleLocation
Indicates that a temple 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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 27, 2026, 6:45 a.m.