Triple
T9133285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heart-Shaped Herb |
E219141
|
entity |
| Predicate | powerSourceExplanation |
P8164
|
FINISHED |
| Object | mutated by vibranium-rich soil |
—
|
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: mutated by vibranium-rich soil | Statement: [Heart-Shaped Herb, powerSourceExplanation, mutated by vibranium-rich soil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerSourceExplanation Context triple: [Heart-Shaped Herb, powerSourceExplanation, mutated by vibranium-rich soil]
-
A.
hasPowerSource
chosen
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
B.
sourceOfPower
Indicates that one entity serves as the origin or provider of power, energy, or authority for another entity.
-
C.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
-
D.
suppliesPowerTo
Indicates that one entity provides electrical or energy power required for the operation or functioning of another entity.
-
E.
powerDependsOn
Indicates that the power or effectiveness of one entity is contingent upon, or influenced by, another entity.
- 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_69ca83debfc0819095800583e97ab10f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8dccecc81908d8fc641c419ca6a |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.