Triple
T31157413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "For a minute there, I lost myself" |
E794247
|
entity |
| Predicate | positionInSong |
P146515
|
FINISHED |
| Object | appears near the end of "Karma Police" |
—
|
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: appears near the end of "Karma Police" | Statement: ["For a minute there, I lost myself", positionInSong, appears near the end of "Karma Police"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInSong Context triple: ["For a minute there, I lost myself", positionInSong, appears near the end of "Karma Police"]
-
A.
positionOnRecord
Indicates the specific place or rank an item occupies within an ordered record or listing.
-
B.
positionInVerse
Indicates the specific ordinal location that something occupies within a verse.
-
C.
positionInOpus
chosen
Indicates the specific location or ordering of a part or element within a larger work or opus.
-
D.
positionOnRemix
Indicates the specific role or placement an entity has within a remix version of a work or composition.
-
E.
discPosition
Indicates the spatial or ordinal placement of a disc relative to a reference point or within a set or structure.
- 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_69f224d504908190b01278dcb7fc3fa7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: April 29, 2026, 9:07 p.m.