Triple
T17560978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeoJSON |
E427694
|
entity |
| Predicate | definedIn |
P775
|
FINISHED |
| Object | RFC 7946 |
—
|
NE NERFINISHED |
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 7946 | Statement: [GeoJSON, definedIn, RFC 7946]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 7946 Context triple: [GeoJSON, definedIn, RFC 7946]
-
A.
RFC 7674
RFC 7674 is an Internet standards document that specifies how to use DANE (DNS-Based Authentication of Named Entities) for securing email transport with TLS.
-
B.
RFC 5906
RFC 5906 is an Internet Engineering Task Force (IETF) standard that specifies Network Time Protocol (NTP) authentication using Autokey public key cryptography.
-
C.
RFC 6146
RFC 6146 is an IETF standard that specifies the behavior and requirements for NAT64, enabling IPv6-only clients to communicate with IPv4 servers through protocol translation.
-
D.
RFC 5546
RFC 5546 is an Internet standards document that specifies the iCalendar Transport-Independent Interoperability Protocol (iTIP) for exchanging calendaring and scheduling information.
-
E.
RFC 5046
RFC 5046 is an IETF standard that defines the marker PDU aligned framing (MPA) protocol used to support RDMA over TCP/IP in the iWARP architecture.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 7946 Target entity description: RFC 7946 is the IETF standard specification that defines the GeoJSON format for encoding geographic data structures in JSON.
-
A.
RFC 7674
RFC 7674 is an Internet standards document that specifies how to use DANE (DNS-Based Authentication of Named Entities) for securing email transport with TLS.
-
B.
RFC 5906
RFC 5906 is an Internet Engineering Task Force (IETF) standard that specifies Network Time Protocol (NTP) authentication using Autokey public key cryptography.
-
C.
RFC 6146
RFC 6146 is an IETF standard that specifies the behavior and requirements for NAT64, enabling IPv6-only clients to communicate with IPv4 servers through protocol translation.
-
D.
RFC 5546
RFC 5546 is an Internet standards document that specifies the iCalendar Transport-Independent Interoperability Protocol (iTIP) for exchanging calendaring and scheduling information.
-
E.
RFC 5046
RFC 5046 is an IETF standard that defines the marker PDU aligned framing (MPA) protocol used to support RDMA over TCP/IP in the iWARP architecture.
- F. None of above. chosen
Provenance (2 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e456267e208190a1238fbe1a535bb0 |
completed | April 19, 2026, 4:12 a.m. |
Created at: April 10, 2026, 5:50 a.m.