Triple
T29939668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corazón Partío |
E760460
|
entity |
| Predicate | hasAcousticVersions |
P147087
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Corazón Partío, hasAcousticVersions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAcousticVersions Context triple: [Corazón Partío, hasAcousticVersions, yes]
-
A.
hasAcousticVersionBy
Indicates that one entity is an acoustic version of another, created or performed by a specified agent.
-
B.
hasLiveAcousticVersion
chosen
Indicates that an entity has a corresponding version that is performed live using acoustic instrumentation.
-
C.
hasAcousticDemoVersion
Indicates that an entity has a version or recording presented in an acoustic demo form.
-
D.
isAcousticReimaginingOf
Indicates that one work is an acoustic reinterpretation or rearranged version of another existing work.
-
E.
hasAudioReleases
Indicates that an entity has associated audio-format releases (such as recordings, tracks, or audio editions) that have been published or made available.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 29, 2026, 6:22 p.m.