Triple

T28586778
Position Surface form Disambiguated ID Type / Status
Subject Devon tin trade E723524 entity
Predicate supportedSettlementType P104748 FINISHED
Object mining towns 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: mining towns | Statement: [Devon tin trade, supportedSettlementType, mining towns]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportedSettlementType
Context triple: [Devon tin trade, supportedSettlementType, mining towns]
  • A. supportsSettlementType chosen
    Indicates that one entity is capable of accommodating, enabling, or being suitable for a particular type or category of settlement.
  • B. settlementType
    Indicates the specific kind or category of human settlement an entity represents, such as a city, village, town, or hamlet.
  • C. connectsSettlementType
    Indicates that there is a relationship linking a settlement to its specific type or classification (e.g., village, town, city).
  • D. governsSettlementType
    Indicates that an authority or administrative body exercises governing control over a particular type or category of settlement.
  • E. typeOfSettlement
    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_69f01d7f92e481909847f5f3f3174a89 completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_6a011d76f3f88190be3d7c9eb0552f34 completed May 11, 2026, 12:06 a.m.
PD Predicate disambiguation batch_6a011cce684881909dd15776bb77a6e0 completed May 11, 2026, 12:03 a.m.
Created at: April 28, 2026, 4:18 a.m.