Triple
T31106844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollow Earth Titans |
E792815
|
entity |
| Predicate | powerSourceAssociation |
P8164
|
FINISHED |
| Object | Hollow Earth power conduits |
—
|
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: Hollow Earth power conduits | Statement: [Hollow Earth Titans, powerSourceAssociation, Hollow Earth power conduits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerSourceAssociation Context triple: [Hollow Earth Titans, powerSourceAssociation, Hollow Earth power conduits]
-
A.
hasPowerSource
chosen
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
B.
powerDependsOn
Indicates that the power or effectiveness of one entity is contingent upon, or influenced by, another entity.
-
C.
suppliesPowerTo
Indicates that one entity provides electrical or energy power required for the operation or functioning of another entity.
-
D.
powerSupplyCapability
Indicates the ability of one entity to provide electrical power to another entity or system.
-
E.
powerCondition
Indicates that one entity’s ability to function, operate, or exert influence depends on a specified power-related requirement or state being satisfied.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 29, 2026, 9:03 p.m.