Triple
T7297488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Mockapetris |
E164560
|
entity |
| Predicate | standardizedIn |
P7508
|
FINISHED |
| Object | RFC 1035 |
E5631
|
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 1035 | Statement: [Paul Mockapetris, standardizedIn, RFC 1035]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1035 Context triple: [Paul Mockapetris, standardizedIn, RFC 1035]
-
A.
RFC 1035
chosen
RFC 1035 is an Internet standards document that defines the implementation details, message formats, and operational procedures for the Domain Name System (DNS).
-
B.
RFC 1034
RFC 1034 is an Internet standards document that specifies the concepts and facilities of the Domain Name System (DNS), defining how domain names are structured and resolved on the internet.
-
C.
RFC Records
RFC Records was a disco-oriented record label founded in the late 1970s by Ray Caviano as a subsidiary of Warner Bros. Records.
-
D.
RFC 1055
RFC 1055 is an early Internet standard that specifies the Serial Line Internet Protocol (SLIP) for transmitting IP packets over serial connections.
-
E.
RFC 1123
RFC 1123 is an Internet standards document that refines and extends the requirements for host software, including DNS and related protocols, to ensure interoperability on the early Internet.
- 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb8e48d48190ada4d507f3b61bc4 |
completed | March 27, 2026, 8:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7e54c25c88190891311b72f242e86 |
completed | March 28, 2026, 2:27 p.m. |
Created at: March 27, 2026, 3 p.m.