Triple
T37149841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magic Keyboard for iPad Pro 11‑inch |
E920333
|
entity |
| Predicate | keyTravel |
P187197
|
FINISHED |
| Object | 1 mm |
—
|
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: 1 mm | Statement: [Magic Keyboard for iPad Pro 11‑inch, keyTravel, 1 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyTravel Context triple: [Magic Keyboard for iPad Pro 11‑inch, keyTravel, 1 mm]
-
A.
coTraveler
Indicates that two or more entities are traveling together along (part of) the same journey or route.
-
B.
travelsFor
Indicates that one entity moves from place to place on behalf of, or for the benefit or purpose of, another entity or objective.
-
C.
travelMechanic
Indicates the method or system by which movement or travel between locations is carried out.
-
D.
travelZone
Indicates a relationship where an entity is located in, moves within, or is permitted to move within a specified geographic or regulatory area.
-
E.
travelMarket
Indicates a relationship where an entity participates in or is associated with the commercial exchange, promotion, or sale of travel-related services or experiences.
- F. None of above. chosen
Provenance (4 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_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb344ba5408190a6fe8face293d88b |
completed | May 6, 2026, 12:30 p.m. |
Created at: May 3, 2026, 4:15 p.m.