Triple
T30741544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muineachán |
E782701
|
entity |
| Predicate | denotesSettlementType |
P1068
|
FINISHED |
| Object | town |
—
|
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: town | Statement: [Muineachán, denotesSettlementType, town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesSettlementType Context triple: [Muineachán, denotesSettlementType, town]
-
A.
settlementType
chosen
Indicates the specific kind or category of human settlement an entity represents, such as a city, village, town, or hamlet.
-
B.
typeOfSettlement
Indicates the specific category or classification of a settlement (e.g., city, town, village) that characterizes what kind of settlement it is.
-
C.
governsSettlementType
Indicates that an authority or administrative body exercises governing control over a particular type or category of settlement.
-
D.
typeOfSettlementRemains
Indicates that one entity specifies the kind or category of settlement remains represented by another entity.
-
E.
connectsSettlementType
Indicates that there is a relationship linking a settlement to its specific type or classification (e.g., village, town, 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:38 p.m.