Triple
T21741656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iPad (8th generation) |
E536672
|
entity |
| Predicate | smartConnector |
P138305
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [iPad (8th generation), smartConnector, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: smartConnector Context triple: [iPad (8th generation), smartConnector, yes]
-
A.
hasSmartConnector
chosen
Indicates that one entity is equipped with or supports a smart connector interface provided by another entity.
-
B.
connectsWorks
Indicates a relationship where one work serves to link, bridge, or associate two or more other works.
-
C.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
D.
commonConnectorName
Indicates that two or more entities share the same connector name used to link or interface them.
-
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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a7250d48190aa63f89db017ef70 |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:49 p.m.