Triple
T35370092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Diocese of Cardiff |
E1021743
|
entity |
| Predicate | hasTerritoryIncluding |
P11790
|
FINISHED |
| Object | City of Cardiff |
—
|
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: City of Cardiff | Statement: [Roman Catholic Diocese of Cardiff, hasTerritoryIncluding, City of Cardiff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerritoryIncluding Context triple: [Roman Catholic Diocese of Cardiff, hasTerritoryIncluding, City of Cardiff]
-
A.
territoryIncluded
chosen
Indicates that one territory is geographically or administratively contained within another territory.
-
B.
territoryRuledIncludes
Indicates that the territory governed or controlled by one entity encompasses or contains the territory of another entity.
-
C.
territoryOriginallyIncluded
Indicates that an earlier or original territorial boundary encompassed the referenced area or entity.
-
D.
sometimesIncludesTerritory
Indicates that one entity occasionally, but not consistently, encompasses or contains the territory of another entity.
-
E.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: May 3, 2026, 4:03 p.m.