Triple
T14965179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roslyn Cemetery |
E373170
|
entity |
| Predicate | hasSettlementTypeAround |
P1068
|
FINISHED |
| Object | 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: village | Statement: [Roslyn Cemetery, hasSettlementTypeAround, village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSettlementTypeAround Context triple: [Roslyn Cemetery, hasSettlementTypeAround, village]
-
A.
hasSettlementAround
Indicates that a settlement is located in the surrounding area of a specified place or feature.
-
B.
isSettlement
Indicates that the subject entity functions as a human-inhabited place or community, such as a town, village, or city.
-
C.
hasTypeOfSettlementComposition
Indicates that an entity is characterized by a particular composition or mix of types of settlements (e.g., urban, rural, suburban) that make up its overall settlement structure.
-
D.
settlementType
chosen
Indicates the specific kind or category of human settlement an entity represents, such as a city, village, town, or hamlet.
-
E.
hasSubsettlement
Indicates that one settlement includes another, smaller settlement as a subordinate or component part.
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6e2fdcc8190bffe603db3388736 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:46 a.m.