Triple
T22565294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dwingeloo |
E557931
|
entity |
| Predicate | hasSettlementStructure |
P64802
|
FINISHED |
| Object | green village |
—
|
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: green village | Statement: [Dwingeloo, hasSettlementStructure, green village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSettlementStructure Context triple: [Dwingeloo, hasSettlementStructure, green village]
-
A.
isSettlement
Indicates that the subject entity functions as a human-inhabited place or community, such as a town, village, or city.
-
B.
hasSubsettlement
Indicates that one settlement includes another, smaller settlement as a subordinate or component part.
-
C.
isSettlementOf
Indicates that one entity is a settlement (such as a town, village, or city) that belongs to, is located within, or is administratively part of another entity.
-
D.
hasSettlementCharacteristic
chosen
Indicates that a settlement possesses a specific attribute, feature, or quality.
-
E.
hasSettlementAround
Indicates that a settlement is located in the surrounding area of a specified place or feature.
- 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_69e11e5ae4ac8190b1f503457603d969 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15fa9ebc8819098d74fb41e14bd7e |
completed | April 29, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:52 p.m.