Triple
T32377668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel WiDi |
E827332
|
entity |
| Predicate | initiallyBundledWith |
P123471
|
FINISHED |
| Object | Intel Wireless Display software |
—
|
NE NERFINISHED |
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: Intel Wireless Display software | Statement: [Intel WiDi, initiallyBundledWith, Intel Wireless Display software]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiallyBundledWith Context triple: [Intel WiDi, initiallyBundledWith, Intel Wireless Display software]
-
A.
bundledStatus
Indicates that an item, service, or component is part of a bundle and specifies its inclusion state or condition within that bundle.
-
B.
initiallyIncluded
chosen
Indicates that an entity was part of a specified set, group, or configuration at the beginning of a process, period, or state.
-
C.
isInitiallyBoundWith
Indicates that two or more entities are connected, associated, or constrained together at the starting point of a process, state, or interaction.
-
D.
builtAsPartOf
Indicates that one entity was constructed as a component or subset of a larger, encompassing entity or project.
-
E.
launchedWith
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 1, 2026, 12:51 a.m.