Triple
T5479166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Security Policy Database |
E123428
|
entity |
| Predicate | predecessorSpecification |
P97
|
FINISHED |
| Object | RFC 2401 |
E325865
|
NE FINISHED |
How this triple was built (3 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 2401 | Statement: [Security Policy Database, predecessorSpecification, RFC 2401]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2401 Context triple: [Security Policy Database, predecessorSpecification, RFC 2401]
-
A.
RFC 2401
chosen
RFC 2401 is an Internet Engineering Task Force (IETF) standard that defines the Security Architecture for the Internet Protocol, forming the core specification for IPsec.
-
B.
RFC 4301
RFC 4301 is an IETF standard that defines the Security Architecture for IP, including the core framework and mechanisms for IPsec-based network security.
-
C.
RFC 2406
RFC 2406 is an Internet standards document that originally specified the Encapsulating Security Payload (ESP) protocol for providing confidentiality, authentication, and integrity in IPsec.
-
D.
RFC 4303
RFC 4303 is an IETF standard that defines the Encapsulating Security Payload (ESP) protocol used to provide confidentiality, integrity, and authentication services in IPsec.
-
E.
RFC 2571
RFC 2571 was an earlier specification in the Simple Network Management Protocol (SNMP) framework that was later superseded and updated by RFC 3411.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorSpecification Context triple: [Security Policy Database, predecessorSpecification, RFC 2401]
-
A.
predecessorControl
Indicates that one entity has control or authority over another entity that precedes it in a sequence, process, or hierarchy.
-
B.
predecessor
chosen
Indicates that one entity comes before another in an ordered sequence or succession.
-
C.
predecessorOperator
Indicates that one operator precedes another in an ordered sequence or process.
-
D.
predecessorState
Indicates that one state directly precedes another in a sequence or process.
-
E.
predecessorModel
Indicates that one model directly precedes another in a sequence, version history, or developmental lineage.
- F. None of above.
Provenance (4 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9247a16c8190ac5a02534da48853 |
completed | March 20, 2026, 6:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf6c7a61848190970a4e34696791eb |
completed | March 22, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.