Triple
T23773206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corey Hart |
E587594
|
entity |
| Predicate | hasHitAlbum |
P102247
|
FINISHED |
| Object | First Offense |
—
|
NE NERFINISHED |
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: First Offense | Statement: [Corey Hart, hasHitAlbum, First Offense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHitAlbum Context triple: [Corey Hart, hasHitAlbum, First Offense]
-
A.
isMajorHitFromAlbum
Indicates that a song is one of the major commercial or popular hits originating from a particular album.
-
B.
hasAssociatedAlbum
chosen
Indicates that an entity is linked to a specific album with which it is related or connected.
-
C.
hasHitSingleOnChart
Indicates that an entity (such as an artist or song) has achieved at least one single that appeared on a specified music chart.
-
D.
hasAlbumVersion
Indicates that one entity is an album-specific version or variant of another entity (such as a track, recording, or work).
-
E.
hasNotableAlbumContext
Indicates that there exists a significant or noteworthy contextual relationship between an entity and a specific album, such as historical, cultural, or artistic relevance.
- 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_69e2490d245881909028226a1393d624 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c467e6588190aab28bc5a8e43e80 |
completed | April 29, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:15 p.m.