Triple
T4050216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menotomy |
E84165
|
entity |
| Predicate | colonialSettlementType |
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: [Menotomy, colonialSettlementType, village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialSettlementType Context triple: [Menotomy, colonialSettlementType, village]
-
A.
settlerType
Indicates the specific category or classification of a settler involved in the relationship or context.
-
B.
humanSettlementType
chosen
Indicates the classification of a human settlement based on its form or function, such as village, town, or city.
-
C.
colonialDesignation
Indicates that one entity assigns or holds a status, name, or classification for another entity within a colonial or colonially imposed framework.
-
D.
hadPrimarySettlementPattern
Indicates that an entity exhibited or was characterized by a particular dominant form or arrangement of human settlement.
-
E.
hasColonialEconomyBasedOn
Indicates that an entity’s colonial economy is primarily structured around or dependent on the specified resource, activity, or economic basis.
- 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_69aed930bd5c819083e7dcc14fc44f69 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb8413848190992e4b5f3b29b43c |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.