Triple
T31143264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mac Giolla Phádraig |
E793847
|
entity |
| Predicate | isHistoricallyLinkedToRegion |
P153540
|
FINISHED |
| Object | Ossory |
—
|
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: Ossory | Statement: [Mac Giolla Phádraig, isHistoricallyLinkedToRegion, Ossory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricallyLinkedToRegion Context triple: [Mac Giolla Phádraig, isHistoricallyLinkedToRegion, Ossory]
-
A.
historicalRegionCorrespondsTo
Indicates that a historical region matches or aligns with a specific region, territory, or administrative unit in terms of location, extent, or identity.
-
B.
isHistoricRegionFor
Indicates that one entity serves as a historically recognized region associated with, or significant to, another entity.
-
C.
historicallyIncludedRegion
Indicates that one region was formerly part of, or contained within, another region during a past historical period.
-
D.
hasHistoricalRegionType
Indicates that a historical region is associated with a specific type or classification of historical region.
-
E.
hasHomeRegionHistorical
chosen
Indicates that an entity is historically associated with or originates from a particular home 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:06 p.m.