Triple
T20876516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parlophone R 5055 |
E514029
|
entity |
| Predicate | hasRunoutInscription |
P142213
|
FINISHED |
| Object | R 5055 A |
—
|
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: R 5055 A | Statement: [Parlophone R 5055, hasRunoutInscription, R 5055 A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRunoutInscription Context triple: [Parlophone R 5055, hasRunoutInscription, R 5055 A]
-
A.
hasTypicalInscriptionMethod
Indicates the usual or characteristic method by which inscriptions are applied or created on an object or surface.
-
B.
hasInscriptions
Indicates that an object, surface, or artifact bears written, carved, or engraved inscriptions on it.
-
C.
hasNoNamesInscribed
Indicates that the entity lacks any names written, carved, or otherwise inscribed on it.
-
D.
hasWinnerEngraved
Indicates that the winner of a competition, event, or award is permanently recorded or inscribed on an associated object or medium.
-
E.
hasNumberOfNamesInscribed
Indicates the quantity of distinct names that are inscribed on a given 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c674f68c8190a7b43aeea5b9b976 |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:45 p.m.