Triple
T2114467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FTP |
E42574
|
entity |
| Predicate | definedIn |
P775
|
FINISHED |
| Object | RFC 959 |
E233815
|
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 959 | Statement: [FTP, definedIn, RFC 959]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 959 Context triple: [FTP, definedIn, RFC 959]
-
A.
RFC 959
chosen
RFC 959 is the foundational Internet standard that defines the File Transfer Protocol (FTP) used for transferring files over TCP/IP networks.
-
B.
RFC 951
RFC 951 is the Internet standard document that specifies the Bootstrap Protocol (BOOTP) used for automatic IP address assignment and basic network configuration of diskless or minimally configured hosts.
-
C.
RFC 854
RFC 854 is the foundational Internet standard that specifies the Telnet protocol for remote, text-based communication over TCP/IP networks.
-
D.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
-
E.
RFC 903
RFC 903 is the Internet standard document that specifies the Reverse Address Resolution Protocol (RARP), which maps link-layer (hardware) addresses to IP addresses in early TCP/IP networks.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb05b51c81908a78c816f492c45c |
completed | March 7, 2026, 5:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae5194abec8190aab8b7a9ef98da92 |
completed | March 9, 2026, 4:50 a.m. |
Created at: March 4, 2026, 7:43 p.m.