Triple
T36763528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Negoiu Peak |
E908271
|
entity |
| Predicate | notableCol |
P205034
|
FINISHED |
| Object | saddle towards Serbota Peak |
—
|
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: saddle towards Serbota Peak | Statement: [Negoiu Peak, notableCol, saddle towards Serbota Peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCol Context triple: [Negoiu Peak, notableCol, saddle towards Serbota Peak]
-
A.
notableDisplay
Indicates that something is prominently or distinctively presented in a way that draws special attention or recognition.
-
B.
notableField
Indicates the field, discipline, or area of activity for which an entity is especially known or distinguished.
-
C.
notableElement
Indicates that an entity has a component, feature, or part that is especially significant, prominent, or noteworthy in relation to it.
-
D.
notableSection
Indicates that a particular part or segment of something is especially important, prominent, or worthy of attention within the whole.
-
E.
notableCollectionFrom
Indicates that one entity is a significant or noteworthy collection originating from, or sourced from, another entity.
- F. None of above. chosen
Provenance (4 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:12 p.m.