Triple
T23728562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dromahair |
E586345
|
entity |
| Predicate | wasMedievalStrongholdOf |
P46785
|
FINISHED |
| Object | O’Rourke clan |
—
|
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: O’Rourke clan | Statement: [Dromahair, wasMedievalStrongholdOf, O’Rourke clan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMedievalStrongholdOf Context triple: [Dromahair, wasMedievalStrongholdOf, O’Rourke clan]
-
A.
wasCitadelOf
Indicates that a place previously served as the main fortified stronghold or central defensive structure for another entity.
-
B.
majorMedievalCity
Indicates that a location was a significant and influential urban center during the medieval period.
-
C.
strongholdOf
chosen
Indicates that a location serves as a primary fortified base, center of power, or main stronghold for a particular entity.
-
D.
historicalStronghold
Indicates that a location has historically served as a fortified center of power, defense, or control for a group or authority.
-
E.
feudalCenter
Indicates that a location serves as the primary seat of authority, administration, or power within a feudal system.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b91740ac81908ca99de0c56f6b57 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:09 p.m.