Triple
T7857579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surface 2 |
E182415
|
entity |
| Predicate | hasVideoOutputPort |
P40470
|
FINISHED |
| Object | micro HDMI |
—
|
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: micro HDMI | Statement: [Surface 2, hasVideoOutputPort, micro HDMI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVideoOutputPort Context triple: [Surface 2, hasVideoOutputPort, micro HDMI]
-
A.
videoOutput
Indicates that one entity produces or provides video signals or content as output to another entity or medium.
-
B.
hasVideoBoard
Indicates that an entity is equipped with or includes a video board (graphics/display hardware component).
-
C.
hasVideoRecordingAvailableOn
Indicates that a video recording of something is accessible or hosted on a specified platform, service, or medium.
-
D.
hasOutputType
Indicates that an entity produces, returns, or yields a result of a specified type.
-
E.
hasPortConnection
chosen
Indicates that one entity is linked to another via a port or interface through which data, power, or signals can be transmitted.
- 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_69ca82887fd48190975896bf38c4596b |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb1a76f8648190976b488d0d8658ef |
completed | March 31, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:52 p.m.