Triple
T18706988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamchiya River basin |
E457396
|
entity |
| Predicate | includesSettlementType |
P104748
|
FINISHED |
| Object | towns |
—
|
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: towns | Statement: [Kamchiya River basin, includesSettlementType, towns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSettlementType Context triple: [Kamchiya River basin, includesSettlementType, towns]
-
A.
isInSettlementType
Indicates that one entity is located within or classified as belonging to a particular type of settlement (such as a city, town, or village).
-
B.
settlementType
Indicates the specific kind or category of human settlement an entity represents, such as a city, village, town, or hamlet.
-
C.
isSettlement
Indicates that the subject entity functions as a human-inhabited place or community, such as a town, village, or city.
-
D.
supportsSettlementType
chosen
Indicates that one entity is capable of accommodating, enabling, or being suitable for a particular type or category of settlement.
-
E.
governsSettlementType
Indicates that an authority or administrative body exercises governing control over a particular type or category of settlement.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e567185c648190848ca47498eb56b3 |
completed | April 19, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.