Triple
T31847932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System Configuration |
E812988
|
entity |
| Predicate | StartupTabFeature |
P102519
|
FINISHED |
| Object | manage startup applications |
—
|
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: manage startup applications | Statement: [System Configuration, StartupTabFeature, manage startup applications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: StartupTabFeature Context triple: [System Configuration, StartupTabFeature, manage startup applications]
-
A.
launcherFeature
chosen
Indicates that one entity functions as a feature, capability, or component provided by a launcher or launching system for another entity.
-
B.
extensionOpened
Indicates that a software extension has been activated or launched from its previously closed or inactive state.
-
C.
launcherType
Indicates the specific kind or category of launcher associated with or used in relation to an entity.
-
D.
launchedFeature
Indicates that an entity has released or made a particular feature available for use.
-
E.
extensionOpenedTo
Indicates that an existing entity has been expanded or lengthened so that a new section or portion is now open or accessible to another 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff41645c548190b7cb4e53079b93ef |
completed | May 9, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69ff410aa33c8190869ba769ac2a93ce |
completed | May 9, 2026, 2:13 p.m. |
Created at: April 30, 2026, 11:50 p.m.