Triple
T28642589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .NET 6 |
E724967
|
entity |
| Predicate | supportEndDate |
P29801
|
FINISHED |
| Object | 2024-11-12 |
—
|
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: 2024-11-12 | Statement: [.NET 6, supportEndDate, 2024-11-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportEndDate Context triple: [.NET 6, supportEndDate, 2024-11-12]
-
A.
supportEndedIn
Indicates that a previously existing support relationship between entities has come to an end at a specific point in time.
-
B.
extendedSupportEndDate
Indicates the date on which an extended support period for something ends.
-
C.
endOfSupportApprox
Indicates that the support period for something is expected to end around a particular time, but the exact end date is approximate rather than precise.
-
D.
sponsorEndDate_HP
Indicates the date on which a sponsorship relationship or agreement comes to an end.
-
E.
mainstreamSupportEndDate
chosen
Indicates the date on which mainstream or primary support for something (such as a product, service, or policy) ends.
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a01b3af7b908190b4675c85d32d106c |
completed | May 11, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_6a01b35813c081908e484b2b9ca5dd05 |
completed | May 11, 2026, 10:45 a.m. |
Created at: April 28, 2026, 4:46 a.m.