Triple
T10900327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7144 |
E257420
|
entity |
| Predicate | replacesSpecificationOf |
P32225
|
FINISHED |
| Object | original iSCSI protocol specification |
—
|
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: original iSCSI protocol specification | Statement: [RFC 7144, replacesSpecificationOf, original iSCSI protocol specification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesSpecificationOf Context triple: [RFC 7144, replacesSpecificationOf, original iSCSI protocol specification]
-
A.
updatesSpecificationOf
chosen
Indicates that one entity revises, modifies, or replaces the existing specification of another entity.
-
B.
replacesComponentOf
Indicates that one entity takes the place of a specific component within another entity, substituting for that component in its role or function.
-
C.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
D.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d761a2f02881908b70be6499dd8d98 |
completed | April 9, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.