Triple
T8083472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HuMP (Hundred Metre Prominence) classification |
E188672
|
entity |
| Predicate | alternativeUnit |
P75161
|
FINISHED |
| Object | feet of prominence |
—
|
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: feet of prominence | Statement: [HuMP (Hundred Metre Prominence) classification, alternativeUnit, feet of prominence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeUnit Context triple: [HuMP (Hundred Metre Prominence) classification, alternativeUnit, feet of prominence]
-
A.
basedUnit
Indicates that one unit is defined in terms of, or derived from, another more fundamental unit.
-
B.
supportedUnit
Indicates that one entity provides assistance, resources, or backing to another entity functioning as a unit or sub-organization.
-
C.
alternativeForm
Indicates that one entity is an alternative version, variant, or representation of another entity.
-
D.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
E.
alternativeUsedBy
chosen
Indicates that one entity serves as an alternative option or substitute that is used in place of another entity.
- 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb415e61ac81909e924aea69a7ff77 |
completed | March 31, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:29 p.m.