Triple
T31745174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brecknockshire |
E810249
|
entity |
| Predicate | currentAreaPartlyIn |
P8403
|
FINISHED |
| Object | Rhondda Cynon Taf |
—
|
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: Rhondda Cynon Taf | Statement: [Brecknockshire, currentAreaPartlyIn, Rhondda Cynon Taf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentAreaPartlyIn Context triple: [Brecknockshire, currentAreaPartlyIn, Rhondda Cynon Taf]
-
A.
currentTerritoryPartlyIn
chosen
Indicates that a territory is currently located such that only a portion of it lies within another specified territory or area.
-
B.
partiallyOn
Indicates that one entity rests or extends over another such that only a portion of its area, volume, or length is supported or in contact.
-
C.
partlyInAdministrativeArea
Indicates that an entity is located such that only a portion of it lies within a specified administrative area (e.g., a city, county, or region).
-
D.
isPartlyProtectedArea
Indicates that an area is subject to some, but not complete, legal or formal protection for conservation or restricted use.
-
E.
partiallyEnclosed
Indicates that one entity surrounds or covers another entity to some extent, but not completely.
- 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_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: April 30, 2026, 11:26 p.m.