Triple
T35559643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salmon of Knowledge |
E1027600
|
entity |
| Predicate | consumedByAccidentally |
P183245
|
FINISHED |
| Object | Fionn mac Cumhaill |
—
|
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: Fionn mac Cumhaill | Statement: [Salmon of Knowledge, consumedByAccidentally, Fionn mac Cumhaill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consumedByAccidentally Context triple: [Salmon of Knowledge, consumedByAccidentally, Fionn mac Cumhaill]
-
A.
consumedByCharacter
Indicates that something (such as an item, resource, or substance) is eaten, drunk, or otherwise used up by a particular character.
-
B.
largelyConsumedBy
Indicates that something is mostly or predominantly eaten or used up by a particular consumer or group.
-
C.
isConsumedBy
Indicates that one entity is eaten, drunk, or otherwise ingested or used up by another entity.
-
D.
swallowed
Indicates that one entity caused another entity to pass from the mouth into the body, typically down the throat.
-
E.
unexpectedConsequenceOf
Indicates that one event, action, or condition occurs as an unforeseen or unintended result of another.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79a53ccc481908421ae16e69aa8a4 |
completed | May 3, 2026, 6:56 p.m. |
Created at: May 3, 2026, 4:04 p.m.