Triple
T27619059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compact Disc |
E700518
|
entity |
| Predicate | alternativeDiameter |
P48665
|
FINISHED |
| Object | 80 mm |
—
|
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: 80 mm | Statement: [Compact Disc, alternativeDiameter, 80 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeDiameter Context triple: [Compact Disc, alternativeDiameter, 80 mm]
-
A.
approximateDiameter
Indicates that one entity specifies the estimated or rough measurement of another entity’s diameter.
-
B.
bodyDiameter
Indicates the measurement of how wide an object's body is across its broadest cross-section.
-
C.
typicalCaseDiameter
chosen
Indicates the usual or standard diameter value associated with an object or case in typical conditions.
-
D.
shellDiameter
Indicates the diameter measurement of a shell, typically specifying the distance across it at its widest point.
-
E.
correctorPlateDiameter
Indicates the relationship where a corrector plate is associated with a specific measurement of its diameter.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 2:13 p.m.