Triple
T30933466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scrantonicity |
E788056
|
entity |
| Predicate | performsCoversOf |
P95695
|
FINISHED |
| Object | The Police (band) |
—
|
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: The Police (band) | Statement: [Scrantonicity, performsCoversOf, The Police (band)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsCoversOf Context triple: [Scrantonicity, performsCoversOf, The Police (band)]
-
A.
containsCoverOf
Indicates that one entity includes within it a cover or covering representation of another entity.
-
B.
hasCoverVersionPerformer
chosen
Indicates that an entity is the performer of a cover version of another entity’s original work.
-
C.
trackCoveredBy
Indicates that one track or path is physically overlaid, shielded, or enclosed by another structure or material.
-
D.
isCoverFor
Indicates that one entity serves as a protective or concealing layer, substitute, or front for another entity or activity.
-
E.
coversFrom
Indicates that one entity provides protection, concealment, or shelter for another entity against something originating from a specified source or direction.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: April 29, 2026, 8:52 p.m.