Triple
T28996561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Last-Modified |
E736181
|
entity |
| Predicate | replacedSpecification |
P32225
|
FINISHED |
| Object | RFC 2616 |
—
|
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: RFC 2616 | Statement: [Last-Modified, replacedSpecification, RFC 2616]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedSpecification Context triple: [Last-Modified, replacedSpecification, RFC 2616]
-
A.
updatesSpecificationOf
chosen
Indicates that one entity revises, modifies, or replaces the existing specification of another entity.
-
B.
replacedStandard
Indicates that one standard has been superseded or taken the place of another standard.
-
C.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
D.
supersededSpecificationIn
Indicates that one specification has been replaced or made obsolete by another specification within a given context or system.
-
E.
replacedDefinitionOf
Indicates that one definition or description has been superseded and taken the place of another.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 28, 2026, 9:31 a.m.