Triple
T2114254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4217 |
E42569
|
entity |
| Predicate | updatesSpecification |
P32225
|
FINISHED |
| Object | FTP security extensions |
—
|
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: FTP security extensions | Statement: [RFC 4217, updatesSpecification, FTP security extensions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatesSpecification Context triple: [RFC 4217, updatesSpecification, FTP security extensions]
-
A.
updatesSpecificationOf
chosen
Indicates that one entity revises, modifies, or replaces the existing specification of another entity.
-
B.
updatedSpecificationDate
Indicates the date on which a specification was last revised or brought up to date.
-
C.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
D.
updatedSpecificationYear
Indicates the year in which the specification for an entity was last revised or updated.
-
E.
updatesVersionOf
Indicates that one entity is a newer or modified version that replaces or supersedes another entity.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb05b51c81908a78c816f492c45c |
completed | March 7, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.