Triple
T2190157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DisplayPort Alt Mode |
E49842
|
entity |
| Predicate | supportsSignalType |
P4618
|
FINISHED |
| Object | DisplayPort video |
—
|
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: DisplayPort video | Statement: [DisplayPort Alt Mode, supportsSignalType, DisplayPort video]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSignalType Context triple: [DisplayPort Alt Mode, supportsSignalType, DisplayPort video]
-
A.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
B.
signalType
chosen
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
C.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
-
D.
supportsProgramType
Indicates that one entity is capable of handling, offering, or being compatible with a specified type of program.
-
E.
compatibleWithSignaling
Indicates that one entity can correctly interpret, process, or operate using the signaling mechanisms, protocols, or formats employed by another entity.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.