Triple
T16852860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LCD TV |
E409716
|
entity |
| Predicate | usesDisplayMode |
P30377
|
FINISHED |
| Object | transmissive display |
—
|
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: transmissive display | Statement: [LCD TV, usesDisplayMode, transmissive display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDisplayMode Context triple: [LCD TV, usesDisplayMode, transmissive display]
-
A.
displayMode
chosen
Indicates how content or information is visually presented or arranged to the user.
-
B.
usesDisplayServer
Indicates that one entity relies on or operates through a display server provided or managed by another entity.
-
C.
usesDisplayServerProtocol
Indicates that one entity operates using, or communicates through, a particular display server protocol provided by another entity.
-
D.
hasDisplayType
Indicates the type or category of display associated with an entity, such as the format, mode, or presentation style used to show its content.
-
E.
usedOnMode
Indicates that something is applied, operated, or functions specifically in a given mode or operational setting.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b37abadc81909d02d329403497d6 |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.