Triple
T3033989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NPAPI |
E82962
|
entity |
| Predicate | deprecatedFor |
P37640
|
FINISHED |
| Object | security reasons |
—
|
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: security reasons | Statement: [NPAPI, deprecatedFor, security reasons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deprecatedFor Context triple: [NPAPI, deprecatedFor, security reasons]
-
A.
deprecatedInVersion
Indicates that something is no longer recommended for use starting from a specified version.
-
B.
deprecatedInRFC
Indicates that a specification, feature, or practice has been formally marked as deprecated within a particular RFC document.
-
C.
usedInsteadOf
Indicates that one entity is employed or chosen as a substitute or replacement for another entity.
-
D.
deprecatedYear
Indicates the year in which something (such as a feature, standard, or item) was officially marked as deprecated or no longer recommended for use.
-
E.
discouragedUsageReason
chosen
Indicates the reason why a particular usage, action, or practice is considered discouraged.
- 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9af13ce48190bda4f5ca0ffe6285 |
completed | March 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ad961e2a408190afb1759132701305 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.