Triple
T8083444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HuMP (Hundred Metre Prominence) classification |
E188672
|
entity |
| Predicate | ignoresCriterion |
P31622
|
FINISHED |
| Object | absolute height |
—
|
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: absolute height | Statement: [HuMP (Hundred Metre Prominence) classification, ignoresCriterion, absolute height]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ignoresCriterion Context triple: [HuMP (Hundred Metre Prominence) classification, ignoresCriterion, absolute height]
-
A.
ignoredBy
Indicates that one entity does not pay attention or respond to another entity.
-
B.
doesNotConsider
chosen
Indicates that one entity fails or chooses not to take another entity or factor into account when forming judgments, decisions, or actions.
-
C.
evaluationCriteriaInclude
Indicates that certain criteria are part of, or explicitly included in, the set of standards used to evaluate something.
-
D.
compositionCriterion
Indicates the rule or standard by which components are selected, combined, or arranged to form a whole.
-
E.
notableCriterion
Indicates that something is distinguished or recognized based on a particular standard, measure, or qualifying condition.
- 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_69cb415cb4688190920868317e77bbff |
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.