Triple
T37658489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SQL Server Native Client |
E937657
|
entity |
| Predicate | deprecationAnnouncedIn |
P42537
|
FINISHED |
| Object | SQL Server 2012 |
—
|
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: SQL Server 2012 | Statement: [SQL Server Native Client, deprecationAnnouncedIn, SQL Server 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deprecationAnnouncedIn Context triple: [SQL Server Native Client, deprecationAnnouncedIn, SQL Server 2012]
-
A.
isDeprecatedInFavorOf
Indicates that something is considered obsolete or no longer recommended because it has been superseded by a specified alternative.
-
B.
deprecatedInVersion
chosen
Indicates that something is no longer recommended for use starting from a specified version.
-
C.
isDeprecatedIn
Indicates that a given entity is considered outdated or no longer recommended for use within a specified context, version, or time frame.
-
D.
isDeprecated
Indicates that the referenced element is considered obsolete and should no longer be used, typically because a preferred alternative exists.
-
E.
isDeprecatedByPublisher
Indicates that a publisher has officially marked the referenced item as deprecated or no longer recommended for use.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.