Triple
T16437351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Here I Go Again reached number 1 on the Billboard Hot 100 |
E399210
|
entity |
| Predicate | releaseFormatOfHitVersion |
P3286
|
FINISHED |
| Object | single |
—
|
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: single | Statement: [Here I Go Again reached number 1 on the Billboard Hot 100, releaseFormatOfHitVersion, single]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseFormatOfHitVersion Context triple: [Here I Go Again reached number 1 on the Billboard Hot 100, releaseFormatOfHitVersion, single]
-
A.
releaseVersion
Indicates the specific version identifier associated with a particular release of something (e.g., software, product, or document).
-
B.
releaseType
chosen
Indicates the kind or category of a release event or version associated with an entity.
-
C.
liveVersionReleasedOn
Indicates the date or time when a live version of something (such as a product, feature, or content) is officially released or made available.
-
D.
subsequentReleaseFormat
Indicates that one media release is issued in a different format that chronologically follows an earlier release of the same content.
-
E.
releaseName
Indicates that an entity is identified or labeled by a specific release name (e.g., version or edition title).
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ba49f3481908e7ea62467ef5813 |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.