Triple
T25281159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liar |
E633827
|
entity |
| Predicate | releasedAsDoubleAAsideWith |
P112602
|
FINISHED |
| Object | Shameless |
—
|
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: Shameless | Statement: [Liar, releasedAsDoubleAAsideWith, Shameless]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasedAsDoubleAAsideWith Context triple: [Liar, releasedAsDoubleAAsideWith, Shameless]
-
A.
isDoubleAAsideWith
chosen
Indicates that two entities are paired together as a double A-side, typically sharing equal prominence in a joint release (such as two lead tracks on the same single).
-
B.
alsoReleased
Indicates that two or more items were released at the same time or as part of the same release event.
-
C.
releasedAsPartOf
Indicates that one entity was issued, launched, or made available as a component or subset of a larger release, collection, or package represented by another entity.
-
D.
releasedWithSingle
Indicates that a work (such as an album or EP) was released together with, or as part of the release of, a specific single.
-
E.
originalReleaseAsBsideOf
Indicates that a work was first released as the B-side of another primary release (such as a single or main track).
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 1:19 p.m.