Triple
T22594934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American 2000 m summits |
E574648
|
entity |
| Predicate | mayAlsoConsider |
P16233
|
FINISHED |
| Object | topographic 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: topographic prominence | Statement: [North American 2000 m summits, mayAlsoConsider, topographic prominence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayAlsoConsider Context triple: [North American 2000 m summits, mayAlsoConsider, topographic prominence]
-
A.
couldConsider
chosen
Indicates that one entity has the potential or option to take another entity into account when making a decision, judgment, or evaluation.
-
B.
mayAlsoAdmit
Indicates that an entity has the option or authority to additionally allow or accept another entity, beyond any primary or default admission.
-
C.
mayAlsoBeProvidedAs
Indicates that something can optionally be supplied or made available in an alternative form or manner in addition to its primary provision.
-
D.
mayAlsoBeCalled
Indicates that one entity can alternatively be referred to by another name or label.
-
E.
mayAdapt
Indicates that one entity is permitted or allowed to modify, adjust, or alter 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f16164d690819096f7c4efb6cedad9 |
completed | April 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:49 p.m.