Triple
T36933782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iPad Pro (11-inch, 1st generation) |
E913554
|
entity |
| Predicate | smartConnectorLocation |
P83502
|
FINISHED |
| Object | back side |
—
|
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: back side | Statement: [iPad Pro (11-inch, 1st generation), smartConnectorLocation, back side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: smartConnectorLocation Context triple: [iPad Pro (11-inch, 1st generation), smartConnectorLocation, back side]
-
A.
busConnectorLocation
Indicates the physical position or placement of a bus connector relative to the system or components it connects.
-
B.
connectsLocation
Indicates a relationship where one entity serves as a link or route that joins or provides access between two locations.
-
C.
connectionLocation
chosen
Indicates the place or spatial context where a connection between entities occurs or is established.
-
D.
locationInCableAssembly
Indicates a relationship where an element is positioned or situated within a specific cable assembly.
-
E.
sensorsLocation
Indicates that a sensor is physically or logically situated at a specific location.
- 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fdf2dc148190bca1bf6bca2e6732 |
completed | May 5, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.