Triple
T37769838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uncanny Inhumans |
E941516
|
entity |
| Predicate | featuresPowerSource |
P8164
|
FINISHED |
| Object | Terrigenesis |
E906133
|
NE 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: Terrigenesis | Statement: [Uncanny Inhumans, featuresPowerSource, Terrigenesis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPowerSource Context triple: [Uncanny Inhumans, featuresPowerSource, Terrigenesis]
-
A.
hasPowerSource
chosen
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
B.
featuresPower
Indicates that one entity provides or includes a specific power capability or power-related function for another entity.
-
C.
powerSupplyCapability
Indicates the ability of one entity to provide electrical power to another entity or system.
-
D.
poweringSystem
Indicates that one entity serves as the source of power or energy that enables the operation or functioning of another entity.
-
E.
suppliesPowerUnitsTo
Indicates that one entity provides electrical power units as a resource or input to another entity.
- F. None of above.
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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40e089658c819084fc00056a5ed3d7 |
completed | June 28, 2026, 8:51 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.