Triple
T28771824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal Services Manager |
E726430
|
entity |
| Predicate | typicalVersionRange |
P11239
|
FINISHED |
| Object | Windows Server 2003 |
—
|
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 Server 2003 | Statement: [Terminal Services Manager, typicalVersionRange, Windows Server 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVersionRange Context triple: [Terminal Services Manager, typicalVersionRange, Windows Server 2003]
-
A.
usedInVersionRange
chosen
Indicates that something is applicable, valid, or in effect only within a specified range of versions.
-
B.
mostCommonVersion
Indicates that the referenced version is the one that occurs or is used more frequently than any other version within a given set or context.
-
C.
principalVersionFor
Indicates a relationship where one version of an entity is designated as the primary or authoritative version for another related entity.
-
D.
currentMajorVersionEffectiveFrom
Indicates the date or point in time from which the current major version of something becomes valid or in effect.
-
E.
versionOf
Indicates that one entity is a specific form, edition, or variant derived from or corresponding 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a011ee3507081908b42de4278ae0b83 |
completed | May 11, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_6a011e874420819091cac3f08e8aa3f9 |
completed | May 11, 2026, 12:10 a.m. |
Created at: April 28, 2026, 6:16 a.m.