Triple
T32137159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flattop Mountain |
E820798
|
entity |
| Predicate | hasNotableNeighbor |
P39585
|
FINISHED |
| Object | Hallett Peak |
—
|
NE NERFINISHED |
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: Hallett Peak | Statement: [Flattop Mountain, hasNotableNeighbor, Hallett Peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableNeighbor Context triple: [Flattop Mountain, hasNotableNeighbor, Hallett Peak]
-
A.
hasNotableConnectionTo
Indicates a significant or noteworthy relationship, association, or link exists between two entities.
-
B.
hasNotableIntersection
Indicates that two entities intersect or cross at a point that is considered significant or noteworthy in some context.
-
C.
hasFewerNeighborsThan
Indicates that one entity is connected to a smaller number of neighboring entities than another entity.
-
D.
hasNotableNearbyEntity
chosen
Indicates that one entity has another significant or noteworthy entity located in its close physical or contextual proximity.
-
E.
hasNotableParent
Indicates that an entity has a parent who is distinguished, prominent, or otherwise notable.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a011d76f3f88190be3d7c9eb0552f34 |
completed | May 11, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_6a011cce684881909dd15776bb77a6e0 |
completed | May 11, 2026, 12:03 a.m. |
Created at: May 1, 2026, 12:30 a.m.