Triple
T9000165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Discman |
E215020
|
entity |
| Predicate | predecessorType |
P9737
|
FINISHED |
| Object | portable cassette player |
—
|
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: portable cassette player | Statement: [Discman, predecessorType, portable cassette player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorType Context triple: [Discman, predecessorType, portable cassette player]
-
A.
predecessorClass
Indicates that one class precedes another in an ordered sequence or hierarchy, typically representing an earlier version or prior stage of that class.
-
B.
predecessorSystemType
chosen
Indicates that one system type functioned as the predecessor or earlier version to another system type.
-
C.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
D.
predecessorRelationship
Indicates that one entity comes before another in an ordered sequence, chain, or lineage, serving as its prior or earlier counterpart.
-
E.
predecessorModel
Indicates that one model directly precedes another in a sequence, version history, or developmental lineage.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc68e3b1f48190bbeafbce363fff53 |
completed | April 1, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_69cc5edd6cb48190b4fc6d6ca0418056 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:05 p.m.