Triple
T11656538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DriverManager |
E277023
|
entity |
| Predicate | replacedByInModernCode |
P21626
|
FINISHED |
| Object | javax.sql.DataSource (recommended) |
—
|
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: javax.sql.DataSource (recommended) | Statement: [DriverManager, replacedByInModernCode, javax.sql.DataSource (recommended)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedByInModernCode Context triple: [DriverManager, replacedByInModernCode, javax.sql.DataSource (recommended)]
-
A.
oftenReplacedBy
Indicates that one entity is frequently substituted or superseded by another in similar contexts or uses.
-
B.
replacedCode
Indicates that one piece of code has been substituted or superseded by another piece of code.
-
C.
modernizedFor
Indicates that something has been updated, adapted, or improved to suit more recent standards, technologies, or conditions.
-
D.
modernEquivalent
chosen
Indicates that one entity serves as the contemporary or updated counterpart of another earlier or traditional entity.
-
E.
mayBeReplacedBy
Indicates that one entity can potentially be substituted or superseded by another entity.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d0331481909682b2e504e4c9a0 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.