Triple
T17840819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blanca Peak |
E445517
|
entity |
| Predicate | positionInNavajoCosmology |
P129382
|
FINISHED |
| Object | sacred mountain of the east |
—
|
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: sacred mountain of the east | Statement: [Blanca Peak, positionInNavajoCosmology, sacred mountain of the east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInNavajoCosmology Context triple: [Blanca Peak, positionInNavajoCosmology, sacred mountain of the east]
-
A.
positionInCosmogony
Indicates the role or place an entity occupies within a culture’s creation or origin narrative of the universe.
-
B.
positionInCosmos
Indicates the spatial or hierarchical location of an entity within the broader structure of the cosmos or universe.
-
C.
positionInAsterism
Indicates the specific location or role that an object occupies within a defined asterism pattern.
-
D.
positionOnMyth
Indicates the relative stance or viewpoint an entity holds regarding a particular myth.
-
E.
positionInConstellation
Indicates the specific location or role an object occupies within the boundaries or structure of a given constellation.
- 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48d2b2ea08190926ec0cf01285833 |
completed | April 19, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3f022ec448190a9bf191be1c5f570 |
completed | April 18, 2026, 8:57 p.m. |
Created at: April 10, 2026, 10:16 a.m.