Triple
T6808183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stevensbeek |
E156360
|
entity |
| Predicate | hasSettlementForm |
P73121
|
FINISHED |
| Object | small 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: small village | Statement: [Stevensbeek, hasSettlementForm, small village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSettlementForm Context triple: [Stevensbeek, hasSettlementForm, small village]
-
A.
hasSettlementAround
Indicates that a settlement is located in the surrounding area of a specified place or feature.
-
B.
hasSettlementOnBanks
Indicates that a settlement is located on or along the banks of a geographic feature such as a river, lake, or coastline.
-
C.
hasSettlementOnUSSide
Indicates that a settlement is located on the United States side of a border or boundary.
-
D.
hasDecisionForm
Indicates that an entity is associated with, or represented by, a particular decision document or formal decision record.
-
E.
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.
- F. None of above. chosen
Provenance (4 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d30b56c48190a5b244ea7e0c669a |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d2a8f9188190abbb8c730e7b5edf |
completed | March 27, 2026, 6:55 p.m. |
Created at: March 27, 2026, 2:16 p.m.