Triple
T21771218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palioseli |
E537432
|
entity |
| Predicate | mountainSettlement |
P78502
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Palioseli, mountainSettlement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainSettlement Context triple: [Palioseli, mountainSettlement, true]
-
A.
mainSettlement
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
-
B.
mountainClusterCity
Indicates a relationship where a city is located within or closely associated with a specific cluster of mountains.
-
C.
mountainFeature
Indicates that one entity is a notable physical or geographical feature associated with, located on, or forming part of a mountain.
-
D.
mainValleySettlements
Indicates that the related entities are the primary or most significant settlements located within a particular valley.
-
E.
isMountainMunicipality
chosen
Indicates that a municipality is classified as being located in a mountainous area or characterized by predominantly mountainous terrain.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031aea8c88190b4bc57df6f269ba6 |
completed | April 28, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:51 p.m.