Triple
T8287450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows Server Core |
E193817
|
entity |
| Predicate | hasInstallationType |
P17153
|
FINISHED |
| Object | clean install |
—
|
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: clean install | Statement: [Windows Server Core, hasInstallationType, clean install]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInstallationType Context triple: [Windows Server Core, hasInstallationType, clean install]
-
A.
hasMajorInstallation
Indicates that one entity possesses, hosts, or contains a primary or significant facility, base, or installation of another entity.
-
B.
typeOfInstallation
chosen
Indicates the specific kind or category of installation associated with an entity (e.g., how or in what form something is installed).
-
C.
requiresInstallation
Indicates that one entity must be installed or set up before the other can be used or become operational.
-
D.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
E.
hasPackageType
Indicates that an entity is associated with or classified under a particular type or category of package.
- 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad4b2008190ad1624e1335147c6 |
completed | March 31, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:52 p.m.