Triple
T18188501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PMC 1240 |
E435474
|
entity |
| Predicate | associatedStereoCatalogueNumber |
P34455
|
FINISHED |
| Object | PCS 3062 |
—
|
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: PCS 3062 | Statement: [PMC 1240, associatedStereoCatalogueNumber, PCS 3062]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedStereoCatalogueNumber Context triple: [PMC 1240, associatedStereoCatalogueNumber, PCS 3062]
-
A.
alternativeCatalogNumber
Indicates that an entity is associated with an additional or substitute catalog number different from its primary catalog identifier.
-
B.
recordLabelCatalogNumber
chosen
Indicates the catalog or identification number assigned to a release by a record label.
-
C.
hasStarFilmCatalogueNumber
Indicates that an entity is associated with a specific catalogue number assigned to a film in the Star film collection.
-
D.
catalogueRaisonneNumber
Indicates the identifier assigned to a work in a catalogue raisonné, linking it to its authoritative scholarly listing.
-
E.
discogsID
Indicates that an entity is associated with a specific identifier used by the Discogs music database to reference it uniquely.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e00059d4819097f681e702fe49e6 |
completed | April 19, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.