Triple
T880414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lesser Caucasus |
E19012
|
entity |
| Predicate | mountainSystemType |
P3559
|
FINISHED |
| Object | folded mountains |
—
|
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: folded mountains | Statement: [Lesser Caucasus, mountainSystemType, folded mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainSystemType Context triple: [Lesser Caucasus, mountainSystemType, folded mountains]
-
A.
mountainSystem
Indicates a relationship where multiple mountains are grouped together as part of the same connected or coherent mountain system or range.
-
B.
mountainRangeType
chosen
Indicates the classification or category of a mountain range based on its geological or geographical type.
-
C.
mountainRange
Indicates that one entity is a mountain range that the other entity is part of, associated with, or located in.
-
D.
sourceMountainRange
Indicates that a river, stream, or similar feature originates from or has its source in a specified mountain range.
-
E.
hasMountainRange
Indicates that one entity possesses, contains, or is geographically associated with a specific mountain range.
- 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_69a4939c32488190a7ccd41cf0abb22b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4accb653c81909fe0753f78145be9 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8eca748190b58e0f08b30fba43 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.