Triple
T6493155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Powell |
E148089
|
entity |
| Predicate | JohnWesleyPowellNotableFor |
P71049
|
FINISHED |
| Object | exploration of the Colorado River |
—
|
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: exploration of the Colorado River | Statement: [Lake Powell, JohnWesleyPowellNotableFor, exploration of the Colorado River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: JohnWesleyPowellNotableFor Context triple: [Lake Powell, JohnWesleyPowellNotableFor, exploration of the Colorado River]
-
A.
notableGlacier
Indicates that the subject is a glacier recognized for its particular significance, prominence, or noteworthiness.
-
B.
notableGorge
Indicates a relationship where a gorge is recognized as notable, significant, or of particular interest in some context.
-
C.
craterLakeNotability
Indicates that an entity is notable or significant specifically for having or being associated with a crater lake.
-
D.
gorgeName
Indicates that an entity has or is identified by the name of a gorge.
-
E.
landerNamedAfter
Indicates that one entity is a lander whose name is derived from, or given in honor of, another entity.
- 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_69c009088f3081909cd467b05919de30 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06ab6abbc8190a4971ad5a654b0cd |
completed | March 22, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69c06740bebc81909d9d6956baa2bcb9 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c067f1ef148190bc0355abe83f7e16 |
completed | March 22, 2026, 10:06 p.m. |
Created at: March 22, 2026, 4:53 p.m.