Triple
T38134715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Tyrone |
E952317
|
entity |
| Predicate | dominantFamilyInRegion |
P59075
|
FINISHED |
| Object | O'Neill dynasty |
—
|
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'Neill dynasty | Statement: [Lord of Tyrone, dominantFamilyInRegion, O'Neill dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantFamilyInRegion Context triple: [Lord of Tyrone, dominantFamilyInRegion, O'Neill dynasty]
-
A.
dominantRegion
Indicates that one region exerts primary control, influence, or prominence over another region within a given context.
-
B.
dominantFamilyPattern
Indicates the prevailing or most influential family structure or relational pattern that characterizes a given context or group.
-
C.
dominanceRegion
Indicates that one entity exerts primary control, influence, or priority over a defined area, range, or scope relative to others.
-
D.
dominantClanFamilies
chosen
Indicates that certain families hold primary power or influence within a clan relative to other families.
-
E.
dominantCommunity
Indicates that one community holds a prevailing or controlling influence, status, or presence over others within a given context.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 3, 2026, 4:21 p.m.