Triple
T29981326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Tahoma Peak |
E761599
|
entity |
| Predicate | isThirdHighest |
P67587
|
FINISHED |
| Object | mountain peak in Washington State |
—
|
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: mountain peak in Washington State | Statement: [Little Tahoma Peak, isThirdHighest, mountain peak in Washington State]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isThirdHighest Context triple: [Little Tahoma Peak, isThirdHighest, mountain peak in Washington State]
-
A.
isThirdLargestIn
Indicates that an entity ranks as the third largest member within a specified group or set based on size or magnitude.
-
B.
isSecondHighest
Indicates that one entity ranks immediately below the highest-ranked entity within a specified ordering or set.
-
C.
thirdRankSee
Indicates that an entity occupying a third rank or position observes, notices, or visually perceives another entity.
-
D.
thirdPlaceRank
chosen
Indicates that an entity holds the third position in a ranking or ordered list relative to others.
-
E.
isThirdInSeries
Indicates that an entity occupies the third position within an ordered sequence or series of related items.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f678d92c4c8190854b1d388e659b7a |
completed | May 2, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:35 p.m.