Triple
T6234948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Money in the Bank |
E139451
|
entity |
| Predicate | hasEnergyLevel |
P40685
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Money in the Bank, hasEnergyLevel, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnergyLevel Context triple: [Money in the Bank, hasEnergyLevel, high]
-
A.
energyLevel
chosen
Indicates the amount or intensity of energy possessed, produced, or exhibited by an entity in a given state or context.
-
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.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
D.
hasFuel
Indicates that an entity possesses or contains fuel available for use.
-
E.
hasEnergyFunction
Indicates that an entity is associated with, governed by, or characterized through a specific energy function.
- 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_69c008b0e7ac8190808a59573ee646f3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062f103a08190b1fb44234832178e |
completed | March 22, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69c05601de6481909d0880048fd7b49a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:22 p.m.