Triple
T7866654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doi Suthep |
E182632
|
entity |
| Predicate | hasStairwayToTemple |
P73575
|
FINISHED |
| Object | Naga staircase |
—
|
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: Naga staircase | Statement: [Doi Suthep, hasStairwayToTemple, Naga staircase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStairwayToTemple Context triple: [Doi Suthep, hasStairwayToTemple, Naga staircase]
-
A.
hasStepsToTemple
chosen
Indicates that one place or structure includes or provides a set of steps leading to a temple.
-
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.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
D.
hasRelocatedTemple
Indicates that a temple has been moved from its original location to a new site.
-
E.
hasNotableTemple
Indicates that an entity is associated with a temple that is recognized as particularly important, famous, or significant.
- 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_69ca82894d9081908a832bfce71a4714 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb38464274819080f182b53783fa84 |
completed | March 31, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:54 p.m.