Triple
T814698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Gambler |
E17625
|
entity |
| Predicate | sideAOrB |
P15273
|
FINISHED |
| Object | A-side 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: A-side single | Statement: [The Gambler, sideAOrB, A-side single]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideAOrB Context triple: [The Gambler, sideAOrB, A-side single]
-
A.
side2
Indicates that an entity is positioned on, associated with, or corresponds to the second side of another entity or structure.
-
B.
side
Indicates that one entity is located at, aligned with, or associated with the lateral part or edge of another entity.
-
C.
supportedSide
Indicates that one entity backed, favored, or provided assistance to a particular side or party in a conflict, dispute, or competition.
-
D.
hasBside
chosen
Indicates that one item serves as the B-side counterpart or secondary track associated with another primary item, typically in a recording or media release.
-
E.
ledBySide1
Indicates that the action, event, or conflict is under the leadership or command of the first participating side (Side 1).
- 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab5035608190bff5f3843b75e662 |
completed | March 1, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69a4aa756920819080ae82948974c876 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.