Triple
T28615609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LineTo |
E724265
|
entity |
| Predicate | supportedSince |
P127933
|
FINISHED |
| Object | early versions of Windows |
—
|
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: early versions of Windows | Statement: [LineTo, supportedSince, early versions of Windows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedSince Context triple: [LineTo, supportedSince, early versions of Windows]
-
A.
supportsSince
Indicates that one entity has been providing support to another entity starting from a specific point in time and continuing thereafter.
-
B.
supportsSinceVersion
chosen
Indicates that a given entity has provided support or compatibility for another entity starting from a specified version onward.
-
C.
supportedFrom
Indicates that one entity provides backing, assistance, or justification for another entity, often serving as the source or basis of that support.
-
D.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
E.
supportedAfter
Indicates that one entity provided support to another only after a specified event, time, or condition had occurred.
- 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_6a015ff02814819094806517fc4c69fa |
completed | May 11, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_6a0154ddd3c48190b85f9f48731cfd8f |
completed | May 11, 2026, 4:02 a.m. |
Created at: April 28, 2026, 4:31 a.m.