Triple
T37784430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Thomond |
E941913
|
entity |
| Predicate | notableDynast |
P127745
|
FINISHED |
| Object | Brian Boru |
E296855
|
NE FINISHED |
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: Brian Boru | Statement: [King of Thomond, notableDynast, Brian Boru]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDynast Context triple: [King of Thomond, notableDynast, Brian Boru]
-
A.
notableDynastyGeneration
Indicates that one dynasty generation is notably significant or distinguished in relation to another within a historical or genealogical context.
-
B.
notableNoble
Indicates that an entity is a noble who is particularly prominent, distinguished, or widely recognized in some notable way.
-
C.
notableFamilyIn
Indicates that a person is notably associated with or belongs to a particular family within a given place or context.
-
D.
notableRoyalHouse
chosen
Indicates that an entity is prominently associated with, or belongs to, a particular royal house or dynasty.
-
E.
hasDynast
Indicates that an entity is associated with or ruled by a particular dynasty.
- F. None of above.
Provenance (4 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a5af1ed1c848190b74250eb9cb49f75 |
completed | July 18, 2026, 3:24 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.