Triple
T9957793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | October 2018 Update (1809) |
E195486
|
entity |
| Predicate | supportPolicy |
P91647
|
FINISHED |
| Object | 18 months of support for Home and Pro editions |
—
|
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: 18 months of support for Home and Pro editions | Statement: [October 2018 Update (1809), supportPolicy, 18 months of support for Home and Pro editions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportPolicy Context triple: [October 2018 Update (1809), supportPolicy, 18 months of support for Home and Pro editions]
-
A.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
-
B.
supportStyle
Indicates the manner or approach by which one entity provides assistance or backing to another.
-
C.
supportRules
Indicates that one entity provides justification, backing, or validation for the rules or constraints defined by another entity.
-
D.
support
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
-
E.
contactPolicy
Indicates the rules or constraints governing how and when one party is allowed to initiate or maintain contact with another.
- F. None of above. chosen
Provenance (4 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6cceb608190ad4424afaddcabfa |
completed | April 2, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd36f112bc81908b473787e702de2f |
completed | April 1, 2026, 3:17 p.m. |
Created at: March 30, 2026, 8:46 p.m.