Triple
T12199642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirty Deeds Done Dirt Cheap |
E290677
|
entity |
| Predicate | catalogNumberAustralia |
P8090
|
FINISHED |
| Object | APLP.020 |
—
|
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: APLP.020 | Statement: [Dirty Deeds Done Dirt Cheap, catalogNumberAustralia, APLP.020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogNumberAustralia Context triple: [Dirty Deeds Done Dirt Cheap, catalogNumberAustralia, APLP.020]
-
A.
alternativeCatalogNumber
Indicates that an entity is associated with an additional or substitute catalog number different from its primary catalog identifier.
-
B.
catalogCode
chosen
Indicates that an entity is assigned a specific catalog identifier or code used for classification or reference.
-
C.
guernseyNumberAtPortAdelaide
Indicates the guernsey (jersey) number that a player wears when playing for the Port Adelaide football club.
-
D.
workCatalogueNumber
Indicates the catalog or reference number assigned to a specific work within an organized catalogue or listing.
-
E.
articleNumber
Indicates that one entity is identified or referenced by a specific article number assigned to it.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d938cd2edc8190b1971349dbc0dee0 |
completed | April 10, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69d91c38321c819080d500d0d64a04f6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:50 p.m.