Triple
T9995385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starro |
E197189
|
entity |
| Predicate | notablePowerSource |
P8164
|
FINISHED |
| Object | psychic energy |
—
|
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: psychic energy | Statement: [Starro, notablePowerSource, psychic energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePowerSource Context triple: [Starro, notablePowerSource, psychic energy]
-
A.
sourceOfPower
Indicates that one entity serves as the origin or provider of power, energy, or authority for another entity.
-
B.
notablePower
Indicates that an entity possesses a significant or distinguished form of power, influence, or capability that is recognized as noteworthy.
-
C.
hasPowerSource
chosen
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
D.
createsPower
Indicates that one entity is the source or generator of power, energy, or influence for another entity or system.
-
E.
suppliesPowerTo
Indicates that one entity provides electrical or energy power required for the operation or functioning of 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_69ca82f3b61c81908ecc2c1c96dbc2e4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdcb99ac74819091f20816478ea375 |
completed | April 2, 2026, 1:51 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:50 p.m.