Triple
T10421197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farnum |
E245653
|
entity |
| Predicate | likelySettlementType |
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: [Farnum, likelySettlementType, village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelySettlementType Context triple: [Farnum, likelySettlementType, village]
-
A.
possibleSettlementAt
Indicates that a settlement could potentially be established or located at a given place or site.
-
B.
settlementType
chosen
Indicates the specific kind or category of human settlement an entity represents, such as a city, village, town, or hamlet.
-
C.
typicalSettlement
Indicates that the subject is a common or characteristic type of settlement typically found in the context of the object.
-
D.
isSettlement
Indicates that the subject entity functions as a human-inhabited place or community, such as a town, village, or city.
-
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.
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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea2bee2081908e5e65df9100d463 |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:11 p.m.