Triple
T10158225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4510 |
E233823
|
entity |
| Predicate | references |
P771
|
FINISHED |
| Object | RFC 4517 |
E239816
|
NE 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 4517 | Statement: [RFC 4510, references, RFC 4517]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4517 Context triple: [RFC 4510, references, RFC 4517]
-
A.
RFC 4517
chosen
RFC 4517 is an Internet standard that specifies the syntaxes and matching rules used in the Lightweight Directory Access Protocol (LDAP).
-
B.
RFC 4515
RFC 4515 is an Internet standard that specifies the string representation of LDAP search filters used in directory service queries.
-
C.
RFC 3417
RFC 3417 is an Internet standard that specifies the transport mappings for the Simple Network Management Protocol (SNMP), defining how SNMP messages are carried over various network protocols such as UDP.
-
D.
RFC 1907
RFC 1907 is an earlier Internet standard that defined the Management Information Base (MIB) for SNMPv2, later superseded by RFC 3418.
-
E.
RFC 4512
RFC 4512 is an IETF specification that defines the core models, schema, and protocol elements for the Lightweight Directory Access Protocol (LDAP) version 3.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec5507f08190b47f797bacd5640c |
completed | April 2, 2026, 4:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d3176ac9388190bc76b3cffce93a3d |
completed | April 6, 2026, 2:16 a.m. |
Created at: March 30, 2026, 9:09 p.m.