Triple
T14790042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iMIP |
E347627
|
entity |
| Predicate | obsoletedDocumentYear |
P32018
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [iMIP, obsoletedDocumentYear, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obsoletedDocumentYear Context triple: [iMIP, obsoletedDocumentYear, 1998]
-
A.
deprecatedYear
chosen
Indicates the year in which something (such as a feature, standard, or item) was officially marked as deprecated or no longer recommended for use.
-
B.
becameObsoleteWhen
Indicates that one thing lost its relevance, usefulness, or validity at the time another specified event, condition, or entity came into existence or took effect.
-
C.
repudiatedInYear
Indicates that the relationship or agreement was formally rejected, renounced, or disowned in the specified year.
-
D.
deposedYear
Indicates the year in which an entity was removed from power or forced out of an official position.
-
E.
eraOfObsolescence
Indicates the time period during which something becomes outdated, no longer useful, or superseded by newer alternatives.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decaa1e9ec81908d7c26c1c4e43014 |
completed | April 14, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.