Triple
T33480582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Peak (Mount Hua) |
E857458
|
entity |
| Predicate | otherMainPeaks |
P131283
|
FINISHED |
| Object | East Peak (Mount Hua) |
—
|
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: East Peak (Mount Hua) | Statement: [North Peak (Mount Hua), otherMainPeaks, East Peak (Mount Hua)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: otherMainPeaks Context triple: [North Peak (Mount Hua), otherMainPeaks, East Peak (Mount Hua)]
-
A.
otherMajorPeak
chosen
Indicates that one peak is another significant or prominent peak associated with, but distinct from, a given primary peak.
-
B.
hasMainMountain
Indicates that an entity is primarily associated with or characterized by a specific mountain as its main or most significant mountain.
-
C.
hasNumberOfMainSummits
Indicates the relationship that specifies how many primary or main summits are associated with a given entity.
-
D.
hasMainPeakElevation_m
Indicates the relationship that specifies the elevation, in meters, of the main or highest peak associated with an entity.
-
E.
moreProminentSummit
Indicates that one summit is higher, more notable, or more significant than another in terms of prominence.
- 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: May 1, 2026, 1:38 a.m.