Triple
T4935380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubbard, Nebraska |
E110797
|
entity |
| Predicate | hasSettlementCategory |
P26700
|
FINISHED |
| Object | rural 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: rural village | Statement: [Hubbard, Nebraska, hasSettlementCategory, rural village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSettlementCategory Context triple: [Hubbard, Nebraska, hasSettlementCategory, rural village]
-
A.
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.
-
B.
hasSettlementAround
Indicates that a settlement is located in the surrounding area of a specified place or feature.
-
C.
settlementType
Indicates the specific kind or category of human settlement an entity represents, such as a city, village, town, or hamlet.
-
D.
hasSettlementOnBanks
Indicates that a settlement is located on or along the banks of a geographic feature such as a river, lake, or coastline.
-
E.
typeOfSettlement
chosen
Indicates the specific category or classification of a settlement (e.g., city, town, village) that characterizes what kind of settlement it is.
- 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_69bd4415eee08190bdce70276e56a5b4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706825188190b854dca5ca2f9db6 |
completed | March 20, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69bd6c389b9881908ad7fb1c5393c1b1 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.