Triple
T38680129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | (You Drive Me) Crazy |
E943869
|
entity |
| Predicate | hasEnergeticProduction |
P196973
|
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: [(You Drive Me) Crazy, hasEnergeticProduction, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnergeticProduction Context triple: [(You Drive Me) Crazy, hasEnergeticProduction, true]
-
A.
hasEnergyResource
Indicates that an entity possesses, controls, or is associated with a source of usable energy.
-
B.
hasEnergyInput
Indicates that an entity receives or requires a specified source or form of energy to operate or occur.
-
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.
hasPowerCapacity
Indicates that an entity possesses a specified amount or limit of power it can produce, handle, or store.
-
E.
usesEnergyFrom
Indicates that one entity derives or consumes energy originating from another entity as its source.
- F. None of above. chosen
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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
| PDg | Predicate description generation | batch_69fe6fe98e38819085100ce4c6cee5b8 |
completed | May 8, 2026, 11:21 p.m. |
Created at: May 3, 2026, 4:33 p.m.