Triple
T30897769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mementos 1971–1987 |
E787073
|
entity |
| Predicate | includesTracksBy |
P66182
|
FINISHED |
| Object | Pure Prairie League |
—
|
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: Pure Prairie League | Statement: [Mementos 1971–1987, includesTracksBy, Pure Prairie League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTracksBy Context triple: [Mementos 1971–1987, includesTracksBy, Pure Prairie League]
-
A.
trackIncluded
Indicates that a particular track is contained within, or forms part of, a larger collection, release, or grouping of tracks.
-
B.
containsAdditionalTracksBeyond
Indicates that one entity includes more tracks or items than are present in another referenced set or version.
-
C.
trackListingIncludes
chosen
Indicates that a track listing contains or features a specific track as one of its listed items.
-
D.
sideAContainsTracksFrom
Indicates that the first entity’s side A includes or features tracks originating from the second entity.
-
E.
sharesTracksWith
Indicates that two entities have one or more tracks in common, such as shared audio, rail, or route segments.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00ae638fcc819096537b2c21366161 |
completed | May 10, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_6a00ae0551988190bcb3564ed9af2847 |
completed | May 10, 2026, 4:10 p.m. |
Created at: April 29, 2026, 8:50 p.m.