Triple
T5861879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Two Hearts Beat As One |
E130293
|
entity |
| Predicate | isHighEnergy |
P40685
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Two Hearts Beat As One, isHighEnergy, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHighEnergy Context triple: [Two Hearts Beat As One, isHighEnergy, true]
-
A.
hasHigh
Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
-
B.
energyLevel
chosen
Indicates the amount or intensity of energy possessed, produced, or exhibited by an entity in a given state or context.
-
C.
hasEnergyRole
Indicates that one entity plays a specific functional role in the production, distribution, management, or use of energy in relation to another entity.
-
D.
energyHigherThan
Indicates that one entity possesses a greater amount or level of energy than another entity.
-
E.
isIntense
Indicates that something exhibits a high degree of strength, force, or concentration in its quality, effect, or activity.
- 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_69c0084f3bb08190a7720f55f7aa4252 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03345ca0c819081c81148d054fed2 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:56 p.m.