Triple
T18188684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parlophone PMC 1240 (mono) |
E435477
|
entity |
| Predicate | isCollectible |
P130157
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Parlophone PMC 1240 (mono), isCollectible, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCollectible Context triple: [Parlophone PMC 1240 (mono), isCollectible, true]
-
A.
isCollectibleFigure
Indicates that an entity is a figure or model intended primarily for collection rather than ordinary use or play.
-
B.
collectibleIn
Indicates that one entity can be collected or obtained within the context, location, or container defined by another entity.
-
C.
collectibleFor
Indicates that one entity is intended or suitable to be collected by, or kept as part of a collection for, another entity.
-
D.
collectibleAspect
Indicates that one entity represents a collectible-related characteristic, feature, or dimension associated with another entity.
-
E.
collects
Indicates that one entity gathers, accumulates, or brings together one or more other entities into its possession or control.
- 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_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. |
| PDg | Predicate description generation | batch_69e438f684e48190b38c64b58c518b6a |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:31 a.m.