Triple
T30597628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battleworld (2015 Secret Wars) |
E778828
|
entity |
| Predicate | powerSourceInStory |
P61281
|
FINISHED |
| Object | Beyonders' power |
—
|
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: Beyonders' power | Statement: [Battleworld (2015 Secret Wars), powerSourceInStory, Beyonders' power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerSourceInStory Context triple: [Battleworld (2015 Secret Wars), powerSourceInStory, Beyonders' power]
-
A.
sourceOfPower
chosen
Indicates that one entity serves as the origin or provider of power, energy, or authority for another entity.
-
B.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
C.
modeOfPower
Indicates the type or method of power or energy by which an entity operates or is driven.
-
D.
powering
Indicates that one entity supplies energy or power that enables another entity to operate or function.
-
E.
powerHarnessedBy
Indicates that a source of power or energy is captured, controlled, or utilized by a particular agent 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 29, 2026, 8:24 p.m.