Triple
T8209338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Study (historic house) |
E191773
|
entity |
| Predicate | situatedInSettlementType |
P14278
|
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: [The Study (historic house), situatedInSettlementType, village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: situatedInSettlementType Context triple: [The Study (historic house), situatedInSettlementType, village]
-
A.
isLocatedInSettlement
Indicates that an entity is situated within or belongs to a specific human settlement, such as a town, village, or city.
-
B.
typicalSettlement
Indicates that the subject is a common or characteristic type of settlement typically found in the context of the object.
-
C.
locatedInOrNearModernSettlement
Indicates that something is situated within or in close proximity to a present-day town, city, or other populated settlement.
-
D.
isInlandSettlement
Indicates that a settlement is located away from the coast, without direct access to the sea or ocean.
-
E.
humanSettlementType
chosen
Indicates the classification of a human settlement based on its form or function, such as village, town, or city.
- 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb76dc784881908e1f63ac907cdd01 |
completed | March 31, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:44 p.m.