Triple
T31142846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Upper Ossory |
E793835
|
entity |
| Predicate | regionHistoricProvince |
P80777
|
FINISHED |
| Object | Leinster |
—
|
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: Leinster | Statement: [Baron Upper Ossory, regionHistoricProvince, Leinster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionHistoricProvince Context triple: [Baron Upper Ossory, regionHistoricProvince, Leinster]
-
A.
historicalProvinceGroup
Indicates that two or more provinces are grouped together based on sharing a common historical administrative or territorial affiliation.
-
B.
locatedInProvinceHistorical
chosen
Indicates that an entity was situated within a specific province during a historical period or according to historical administrative boundaries.
-
C.
historicalRegion
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
-
D.
historicalRegionCode
Indicates that an entity is associated with a specific code identifying a historical region.
-
E.
historicalAdministrativeRegionName
Indicates the name assigned to an administrative region as it existed during a specific historical period.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 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: April 29, 2026, 9:06 p.m.