Triple
T23382720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O'Donovan |
E593793
|
entity |
| Predicate | clanTerritoryHistorically |
P24920
|
FINISHED |
| Object | County Cork |
—
|
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: County Cork | Statement: [O'Donovan, clanTerritoryHistorically, County Cork]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clanTerritoryHistorically Context triple: [O'Donovan, clanTerritoryHistorically, County Cork]
-
A.
hasHistoricTerritory
chosen
Indicates that an entity possesses or claims a territory that it historically occupied, controlled, or was associated with in the past.
-
B.
territoryAtTime
Indicates that a specified territory is associated with or held by an entity during a particular time or time interval.
-
C.
historicalTerritoryType
Indicates that a territory is classified according to a specific type or category it held during a historical period.
-
D.
historicalRegionOfInfluence
Indicates that one entity was historically within the geographic, political, or cultural sphere of influence of another entity.
-
E.
landsPreviouslyBelongedTo
Indicates that the specified lands were owned, controlled, or possessed by a different party at an earlier time.
- 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_69e25d268a50819095f2fd479da8ef3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3b9287481908fd86c41f6d9fc53 |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:34 p.m.