Triple
T35332265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloch wall |
E1020352
|
entity |
| Predicate | hasEnergyContribution |
P58869
|
FINISHED |
| Object | exchange 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: exchange energy | Statement: [Bloch wall, hasEnergyContribution, exchange energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnergyContribution Context triple: [Bloch wall, hasEnergyContribution, exchange energy]
-
A.
energyContribution
chosen
Indicates the amount or role of energy that one entity provides or contributes to another entity, process, or system.
-
B.
hasEnergyRole
Indicates that one entity plays a specific functional role in the production, distribution, management, or use of energy in relation to another entity.
-
C.
hasEnergyResource
Indicates that an entity possesses, controls, or is associated with a source of usable energy.
-
D.
hasEnergyInput
Indicates that an entity receives or requires a specified source or form of energy to operate or occur.
-
E.
usesEnergyFrom
Indicates that one entity derives or consumes energy originating from another entity as its source.
- 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 3, 2026, 4:03 p.m.