Triple
T30926811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Branch |
E787878
|
entity |
| Predicate | influencedLaterLiterature |
P18315
|
FINISHED |
| Object | Irish heroic romance |
—
|
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: Irish heroic romance | Statement: [Red Branch, influencedLaterLiterature, Irish heroic romance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influencedLaterLiterature Context triple: [Red Branch, influencedLaterLiterature, Irish heroic romance]
-
A.
literaryInfluence
chosen
Indicates that one entity has had a significant impact on the style, themes, or development of another entity’s literary work.
-
B.
wereInfluencedBy
Indicates that one entity’s ideas, actions, or characteristics were shaped or affected by another entity.
-
C.
hasLiterarySignificance
Indicates that something holds notable importance, influence, or value within the realm of literature or literary studies.
-
D.
influencesFromAuthor
Indicates that one entity is affected or shaped by the actions, ideas, or characteristics of an author.
-
E.
hasHistoricalWritingInfluenceFrom
Indicates that one entity’s historical writing style, content, or traditions are influenced by those of 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 29, 2026, 8:51 p.m.