Triple
T31745173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brecknockshire |
E810249
|
entity |
| Predicate | currentAreaNowMostlyIn |
P8402
|
FINISHED |
| Object | Powys |
—
|
NE NERFINISHED |
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: Powys | Statement: [Brecknockshire, currentAreaNowMostlyIn, Powys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentAreaNowMostlyIn Context triple: [Brecknockshire, currentAreaNowMostlyIn, Powys]
-
A.
currentTerritoryMostlyIn
chosen
Indicates that the majority of the current territorial area of one entity lies within the territorial boundaries of another entity.
-
B.
areaRuledNowIn
Indicates that a region is currently governed or controlled by a specified ruling authority or entity.
-
C.
coreAreaNowIn
Indicates that an entity’s primary or central area is currently located within or part of another specified area.
-
D.
currentTerritoryPartlyIn
Indicates that a territory is currently located such that only a portion of it lies within another specified territory or area.
-
E.
administrativeRegionMostlyCoincidesWith
Indicates that the spatial extent of one administrative region substantially overlaps and aligns with that of another, with only minor differences in boundaries.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: April 30, 2026, 11:26 p.m.