Triple
T37051808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DisplayPort Single-Stream Transport |
E917068
|
entity |
| Predicate | canBeCarriedOver |
P136075
|
FINISHED |
| Object | full-size DisplayPort connector |
—
|
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: full-size DisplayPort connector | Statement: [DisplayPort Single-Stream Transport, canBeCarriedOver, full-size DisplayPort connector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeCarriedOver Context triple: [DisplayPort Single-Stream Transport, canBeCarriedOver, full-size DisplayPort connector]
-
A.
carriedOver
chosen
Indicates that something from a previous context, state, or period is transferred and remains applicable or in effect in the current one.
-
B.
carriedFor
Indicates that one entity transported or bore another entity on behalf of or for the benefit of that other entity.
-
C.
canBeExceededIn
Indicates that one entity’s value, level, or extent is capable of being surpassed by that of another entity within a specified context.
-
D.
canBeUsedOver
Indicates that one entity is suitable or valid for use in place of, or in relation to, another entity.
-
E.
carryforwardRule
Indicates a rule that governs how unused amounts (such as losses, credits, or balances) are transferred and applied from one period to subsequent periods.
- 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: May 3, 2026, 4:14 p.m.