Triple
T29664762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baby, I Love Your Way |
E750497
|
entity |
| Predicate | hasSubsequentMedium |
P78290
|
FINISHED |
| Object | live album track |
—
|
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: live album track | Statement: [Baby, I Love Your Way, hasSubsequentMedium, live album track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubsequentMedium Context triple: [Baby, I Love Your Way, hasSubsequentMedium, live album track]
-
A.
hasSubsequent
Indicates that one entity occurs, appears, or is positioned after another in a defined sequence or order.
-
B.
subsequentMedium
chosen
Indicates that one medium or format follows another in a sequence, typically as a later or alternative form of the same content or communication.
-
C.
hasSubsequentStandard
Indicates that one standard is followed or superseded by another standard that comes after it in sequence or version.
-
D.
hasAssociatedMedium
Indicates that one entity is linked to another entity that serves as its medium, format, or channel of expression or transmission.
-
E.
hasSubsequentVersion
Indicates that one entity is a later or updated version that follows another entity in a version sequence.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: April 28, 2026, 7 p.m.