Triple
T34973436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia KC 32847 |
E1008602
|
entity |
| Predicate | sideAContainsTracksFrom |
P182156
|
FINISHED |
| Object | Get Your Wings |
—
|
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: Get Your Wings | Statement: [Columbia KC 32847, sideAContainsTracksFrom, Get Your Wings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideAContainsTracksFrom Context triple: [Columbia KC 32847, sideAContainsTracksFrom, Get Your Wings]
-
A.
side1Track
Indicates that an entity is associated with or belongs to the first side or track in a two-sided or multi-track configuration.
-
B.
containsAdditionalTracksBeyond
Indicates that one entity includes more tracks or items than are present in another referenced set or version.
-
C.
isBsideTrack
Indicates that one track is the B-side counterpart associated with another primary (A-side) track, typically on a single release.
-
D.
sideThreeTrack
Indicates that an entity is associated with, or corresponds to, the third side (or track) in a multi-sided or multi-track context.
-
E.
A-sideWith
Indicates that one entity is aligned or positioned on the same side as another entity.
- F. None of above. chosen
Provenance (4 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7870dfe108190996c0c68630edc7f |
completed | May 3, 2026, 5:34 p.m. |
Created at: May 3, 2026, 4:01 p.m.