Triple
T9456354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | oersted |
E228023
|
entity |
| Predicate | isDeprecatedIn |
P88270
|
FINISHED |
| Object | modern SI practice |
—
|
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: modern SI practice | Statement: [oersted, isDeprecatedIn, modern SI practice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDeprecatedIn Context triple: [oersted, isDeprecatedIn, modern SI practice]
-
A.
isDeprecatedByPublisher
Indicates that a publisher has officially marked the referenced item as deprecated or no longer recommended for use.
-
B.
isNotDeprecated
Indicates that something is currently considered active or supported and has not been marked as deprecated.
-
C.
deprecatedInVersion
Indicates that something is no longer recommended for use starting from a specified version.
-
D.
deprecatedInRFC
Indicates that a specification, feature, or practice has been formally marked as deprecated within a particular RFC document.
-
E.
methodIntroducedWith
Indicates that one method is introduced, defined, or presented together with another method as part of the same conceptual or procedural context.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f8f7e1481909318e473ab4d6460 |
completed | April 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69cca5596ffc819097e9c8eefd4ef9b8 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:52 p.m.