Triple
T28614055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnifier |
E724234
|
entity |
| Predicate | canBeLaunchedVia |
P33533
|
FINISHED |
| Object | Windows Settings |
—
|
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: Windows Settings | Statement: [Magnifier, canBeLaunchedVia, Windows Settings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeLaunchedVia Context triple: [Magnifier, canBeLaunchedVia, Windows Settings]
-
A.
launchedVia
chosen
Indicates that an entity is initiated, deployed, or started by means of a specified method, mechanism, or intermediary.
-
B.
launchesSupported
Indicates that one entity is capable of initiating or starting another entity or process.
-
C.
launchedWith
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
-
D.
launchedUnder
Indicates that one entity was initiated, started, or brought into operation under the authority, auspices, or framework of another entity (such as a program, organization, or policy).
-
E.
launcherType
Indicates the specific kind or category of launcher associated with or used in relation to an entity.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 28, 2026, 4:31 a.m.