Triple
T35481783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackfyre |
E1025488
|
entity |
| Predicate | passedTo |
P1308
|
FINISHED |
| Object | Daemon Blackfyre |
—
|
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: Daemon Blackfyre | Statement: [Blackfyre, passedTo, Daemon Blackfyre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passedTo Context triple: [Blackfyre, passedTo, Daemon Blackfyre]
-
A.
passed
Indicates that one entity successfully transferred control, responsibility, or an item (such as an object, message, or test) to another entity or through a specified stage or condition.
-
B.
passes
chosen
Indicates that one entity successfully transfers, hands over, or moves something (such as an object, message, or responsibility) to another entity.
-
C.
passesUnder
Indicates that one entity moves or extends beneath another entity, typically crossing below it without direct contact.
-
D.
isPassedThroughBy
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
-
E.
passedAlongside
Indicates that one entity moved or traveled next to another entity along the same route or path, maintaining a roughly parallel course.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.