Triple
T14898375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iunet |
E359936
|
entity |
| Predicate | hasMainTempleOrientation |
P111924
|
FINISHED |
| Object | roughly east-west |
—
|
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: roughly east-west | Statement: [Iunet, hasMainTempleOrientation, roughly east-west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainTempleOrientation Context triple: [Iunet, hasMainTempleOrientation, roughly east-west]
-
A.
mainShrineOrientation
chosen
Indicates the directional alignment or facing direction of a main shrine relative to a reference point or axis.
-
B.
hasGoddessShrineOrientation
Indicates the directional orientation or alignment of a shrine dedicated to a goddess in relation to a reference point or axis.
-
C.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
D.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded6084574819098033a9723f3e1c4 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:11 a.m.