Triple
T20326100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nico Minoru |
E492341
|
entity |
| Predicate | magicTrigger |
P139694
|
FINISHED |
| Object | blood |
—
|
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: blood | Statement: [Nico Minoru, magicTrigger, blood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magicTrigger Context triple: [Nico Minoru, magicTrigger, blood]
-
A.
usesMagic
Indicates that an entity performs actions or achieves effects by employing magical powers or supernatural abilities.
-
B.
magicField
Indicates the presence or influence of a magical force or energy affecting an entity or area.
-
C.
usesMagicFor
Indicates that one entity employs or applies magic as a means to achieve, affect, or perform something involving another entity or context.
-
D.
magicWord
Indicates that an entity is a special word or phrase that, when used, triggers a particular effect, action, or access.
-
E.
magicAffinity
Indicates a relationship where an entity possesses a natural connection to, talent for, or compatibility with magical forces or energies.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e4130081909ec54f131939e442 |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:21 a.m.