Triple
T14716221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Lyons |
E345686
|
entity |
| Predicate | coversRegionType |
P97770
|
FINISHED |
| Object | rural |
—
|
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 | Statement: [Division of Lyons, coversRegionType, rural]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversRegionType Context triple: [Division of Lyons, coversRegionType, rural]
-
A.
containsRegionType
chosen
Indicates that one region includes or encompasses another region of a specified type within its spatial or logical boundaries.
-
B.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
C.
includedSpecialRegionType
Indicates that a special or designated region is included within another region or context, specifying the type of that included special region.
-
D.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
E.
supportsRegion
Indicates that one entity provides assistance, resources, or backing to a specific geographic or administrative region.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb98688f48190b2b19ce7aa06a6db |
completed | April 14, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.