Triple
T35941440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Blacksmith of Ballinalee |
E1039453
|
entity |
| Predicate | hasRoleOfBearer |
P161
|
FINISHED |
| Object | IRA commander |
—
|
LITERAL 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: IRA commander | Statement: [The Blacksmith of Ballinalee, hasRoleOfBearer, IRA commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleOfBearer Context triple: [The Blacksmith of Ballinalee, hasRoleOfBearer, IRA commander]
-
A.
hasRole
chosen
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
B.
hasNameBearerRole
Indicates that an entity holds or fulfills the role of bearing or carrying a particular name.
-
C.
associatedWithRoleOfNameBearer
Indicates that an entity is connected to or involved with the specific role or function held by a designated name bearer.
-
D.
bearerInstanceOf
Indicates that a bearer (such as an agent, object, or entity) is an instance or specific realization of a more general class, type, or role.
-
E.
hasAuthorityOf
Indicates that one entity possesses and can exercise the official power, rights, or control that properly belong to another entity.
- 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_69f76e24bbd0819096b837d35371639a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: May 3, 2026, 4:07 p.m.