Triple
T37149560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iPhone 5 and later (non-USB-C models) |
E920326
|
entity |
| Predicate | doesNotUseConnectorType |
P133324
|
FINISHED |
| Object | USB-C |
—
|
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: USB-C | Statement: [iPhone 5 and later (non-USB-C models), doesNotUseConnectorType, USB-C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotUseConnectorType Context triple: [iPhone 5 and later (non-USB-C models), doesNotUseConnectorType, USB-C]
-
A.
doesNotUse
Indicates that one entity intentionally refrains from employing, utilizing, or relying on another entity, method, or resource.
-
B.
doesNotUseComponent
chosen
Indicates that one entity explicitly avoids or omits using a particular component in its structure, behavior, or implementation.
-
C.
hasNoConnectionType
Indicates that there is explicitly no defined type or category of connection between the related entities.
-
D.
usedConnectorInVersion3
Indicates that a specific connector was utilized in the third version of a system, product, or configuration.
-
E.
hasConnector
Indicates that one entity is linked or joined to another entity through a connector or connecting element.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.