Triple
T25933247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderbolt 4 |
E653483
|
entity |
| Predicate | supportsAlternativeMode |
P57778
|
FINISHED |
| Object | DisplayPort Alt Mode |
—
|
NE NERFINISHED |
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 Alt Mode | Statement: [Thunderbolt 4, supportsAlternativeMode, DisplayPort Alt Mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAlternativeMode Context triple: [Thunderbolt 4, supportsAlternativeMode, DisplayPort Alt Mode]
-
A.
supportedMode
Indicates that a system, device, or component is capable of operating in or handling a particular mode.
-
B.
alternateMode
chosen
Indicates that one entity functions as an alternative form, configuration, or mode of operation for another entity.
-
C.
hasAlternativeMedium
Indicates that an entity is available, expressed, or presented in another medium or format as an alternative to its primary one.
-
D.
hasModeSwitching
Indicates that an entity supports changing between different operational modes or states.
-
E.
alsoSupports
Indicates that an entity, in addition to its primary or previously stated function, provides support for another entity, feature, or activity.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 22, 2026, 8:37 a.m.