Triple
T30926784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Branch |
E787878
|
entity |
| Predicate | basedInLegend |
P195238
|
FINISHED |
| Object | Emain Macha |
—
|
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: Emain Macha | Statement: [Red Branch, basedInLegend, Emain Macha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedInLegend Context triple: [Red Branch, basedInLegend, Emain Macha]
-
A.
inLegendRole
Indicates that an entity appears in a legendary or mythic context fulfilling a specific narrative or symbolic role.
-
B.
mentionsLegend
Indicates that one entity makes reference to or cites a legendary figure, story, or concept associated with another entity.
-
C.
knownAsLegend
Indicates that an entity is widely regarded or celebrated as a legend.
-
D.
bestKnownLegend
Indicates that one entity is the most prominent or widely recognized legendary story or myth associated with another entity.
-
E.
featuredLegend
Indicates that an entity is highlighted or showcased as a prominent or notable legend within a given context.
- F. None of above. chosen
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_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
| PDg | Predicate description generation | batch_69fdb3172b808190b590d7c5be31ebb7 |
completed | May 8, 2026, 9:55 a.m. |
Created at: April 29, 2026, 8:51 p.m.