Triple
T1054615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jon Postel |
E22773
|
entity |
| Predicate | positionHeld |
P8
|
FINISHED |
| Object | RFC Editor |
E35272
|
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 Editor | Statement: [Jon Postel, positionHeld, RFC Editor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC Editor Context triple: [Jon Postel, positionHeld, RFC Editor]
-
A.
RFC Editor
chosen
The RFC Editor is the organization responsible for editing, publishing, and maintaining the Request for Comments (RFC) series that documents standards and technical notes for the Internet community.
-
B.
RFCs
RFCs (Requests for Comments) are a series of technical and organizational documents that define and standardize protocols, procedures, and policies for the Internet and related networks.
-
C.
IETF Secretariat
The IETF Secretariat is the administrative body that supports the operations, documentation, and processes of the Internet Engineering Task Force.
-
D.
IETF Area Directors
IETF Area Directors are senior leaders within the Internet Engineering Task Force responsible for managing specific technical areas and guiding the development of Internet standards.
-
E.
RFC 882
RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
- 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8d79268819080f3f3f497e91c58 |
completed | March 1, 2026, 10:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac3bd110ac8190b66163de42bd3034 |
completed | March 7, 2026, 2:53 p.m. |
Created at: March 1, 2026, 7:42 p.m.