Triple
T10919982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taskmaster |
E257921
|
entity |
| Predicate | powerOrigin |
P61281
|
FINISHED |
| Object | experimental serum |
—
|
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: experimental serum | Statement: [Taskmaster, powerOrigin, experimental serum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerOrigin Context triple: [Taskmaster, powerOrigin, experimental serum]
-
A.
sourceOfPower
chosen
Indicates that one entity serves as the origin or provider of power, energy, or authority for another entity.
-
B.
powerplantOrigin
Indicates that a power plant originates from, is sourced in, or is associated with a particular geographic location or administrative region.
-
C.
primaryPower
Indicates that one entity serves as the main or dominant source of power or energy for another entity.
-
D.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
E.
createsPower
Indicates that one entity is the source or generator of power, energy, or influence for another entity or system.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77081a0c48190b7aa4a482032d1ea |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:22 p.m.