Triple
T30926808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Branch |
E787878
|
entity |
| Predicate | relatedGroupInMythology |
P54299
|
FINISHED |
| Object | Fianna |
E1341996
|
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: Fianna | Statement: [Red Branch, relatedGroupInMythology, Fianna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedGroupInMythology Context triple: [Red Branch, relatedGroupInMythology, Fianna]
-
A.
linkedToMythology
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
B.
ethnicGroupInMythologyOf
Indicates that a particular ethnic group appears within, is featured by, or is thematically represented in the mythology or mythological traditions of another culture or group.
-
C.
mythologicalCategory
chosen
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
D.
centralMythology
Indicates that one entity serves as a core or defining mythological element within the context or tradition of another entity.
-
E.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28e46dab3081908ba0332d4a0e277a |
completed | June 10, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:51 p.m.