Triple
T9000922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitsubishi Diamondtron |
E215035
|
entity |
| Predicate | screenGeometry |
P85628
|
FINISHED |
| Object | flat screen (in later models) |
—
|
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: flat screen (in later models) | Statement: [Mitsubishi Diamondtron, screenGeometry, flat screen (in later models)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenGeometry Context triple: [Mitsubishi Diamondtron, screenGeometry, flat screen (in later models)]
-
A.
viewGeometry
Indicates a relationship where a particular viewpoint or camera setup defines how a scene’s geometry is projected, framed, or visually represented.
-
B.
displayResolution
Indicates the relationship specifying the width and height dimensions at which visual content is rendered or shown on a display.
-
C.
integratedDisplaySize
Indicates the size or dimensions of a built-in or non-detachable display associated with an entity.
-
D.
externalDisplaySize
Indicates the size or dimensions of an external display associated with an entity.
-
E.
graphicsDimension
Indicates a relationship where an entity has or is associated with a specific graphical size or dimensional properties.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6954bb1881908d004a26ba7fe360 |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edd6cb48190b4fc6d6ca0418056 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:05 p.m.