Triple
T33121043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prebaetic System |
E847595
|
entity |
| Predicate | mountainSystemOf |
P945
|
FINISHED |
| Object | Baetic Cordillera |
—
|
NE NERFINISHED |
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: Baetic Cordillera | Statement: [Prebaetic System, mountainSystemOf, Baetic Cordillera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainSystemOf Context triple: [Prebaetic System, mountainSystemOf, Baetic Cordillera]
-
A.
mountainSystem
chosen
Indicates a relationship where multiple mountains are grouped together as part of the same connected or coherent mountain system or range.
-
B.
mountainRange
Indicates that one entity is a mountain range that the other entity is part of, associated with, or located in.
-
C.
sourceMountainRange
Indicates that a river, stream, or similar feature originates from or has its source in a specified mountain range.
-
D.
mountainRangeType
Indicates the classification or category of a mountain range based on its geological or geographical type.
-
E.
parentMountain
Indicates that one mountain is considered the larger or primary "parent" from which another, related "child" mountain is derived or associated.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d718e52c81908e158907db3ec765 |
completed | May 3, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.