Triple
T24174804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8859-16 |
E599248
|
entity |
| Predicate | isSupersededInPracticeBy |
P101
|
FINISHED |
| Object | Unicode |
—
|
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: Unicode | Statement: [ISO/IEC 8859-16, isSupersededInPracticeBy, Unicode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSupersededInPracticeBy Context triple: [ISO/IEC 8859-16, isSupersededInPracticeBy, Unicode]
-
A.
wasSupersededBy
chosen
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
B.
supersededInPrecisionBy
Indicates that one entity’s level of precision has been replaced or overtaken by another entity’s greater precision.
-
C.
supersededSpecificationIn
Indicates that one specification has been replaced or made obsolete by another specification within a given context or system.
-
D.
repealsOrSupersedes
Indicates that one legal act, rule, or provision invalidates, replaces, or takes precedence over another.
-
E.
abolishedInEffectBy
Indicates that the legal force or practical operation of something is nullified or terminated as a result of another specified action or measure.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:33 p.m.