Triple
T35980706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cerros de Mavecure |
E1040554
|
entity |
| Predicate | numberOfMainHills |
P79004
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Cerros de Mavecure, numberOfMainHills, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfMainHills Context triple: [Cerros de Mavecure, numberOfMainHills, 3]
-
A.
hasApproximateNumberOfHills
Indicates that an entity is associated with an estimated or imprecise count of hills rather than an exact number.
-
B.
numberOfMountains
Indicates the quantitative count of mountains associated with a given entity or context.
-
C.
hasMainMountain
Indicates that an entity is primarily associated with or characterized by a specific mountain as its main or most significant mountain.
-
D.
hasNumberOfMainSummits
chosen
Indicates the relationship that specifies how many primary or main summits are associated with a given entity.
-
E.
hasMainPeakElevation_m
Indicates the relationship that specifies the elevation, in meters, of the main or highest peak associated with an 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.