Triple
T1869503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6241 |
E39001
|
entity |
| Predicate | rfcNumber |
P26175
|
FINISHED |
| Object | 6241 |
—
|
LITERAL 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: 6241 | Statement: [RFC 6241, rfcNumber, 6241]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rfcNumber Context triple: [RFC 6241, rfcNumber, 6241]
-
A.
originalRfc
Indicates that something is the initial or authoritative RFC (Request for Comments) document from which a specification, standard, or later revision originates.
-
B.
refnum
chosen
Indicates that an entity is associated with a specific reference number used to identify or track it.
-
C.
relatedRFC
Indicates that one resource or specification is connected or associated with another through a shared or relevant RFC (Request for Comments) document.
-
D.
protocolNumber
Indicates the specific identifying number assigned to a protocol that governs or documents an interaction, process, or agreement between entities.
-
E.
opusNumber
Indicates that a creative work is assigned a specific opus number identifying its place within a creator’s catalog or chronological sequence of works.
- F. None of above.
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_69a8862f7074819096afe7fe65e179e9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb16c09e48190a345c95eab59fd87 |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe02c3c819093a4744b476106ca |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.