Triple
T34345146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRTF Stream |
E881409
|
entity |
| Predicate | describedInRFC |
P519
|
FINISHED |
| Object | RFC 5742 |
—
|
NE NERFINISHED |
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 5742 | Statement: [IRTF Stream, describedInRFC, RFC 5742]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedInRFC Context triple: [IRTF Stream, describedInRFC, RFC 5742]
-
A.
hasRFC
Indicates that an entity is associated with, described by, or defined in a specific RFC (Request for Comments) document.
-
B.
deprecatedInRFC
Indicates that a specification, feature, or practice has been formally marked as deprecated within a particular RFC document.
-
C.
originalRfc
Indicates that something is the initial or authoritative RFC (Request for Comments) document from which a specification, standard, or later revision originates.
-
D.
describedIn
chosen
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
E.
describedAsIn
Indicates that one entity is described or characterized in a particular way within a specified information source or context.
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 1, 2026, 1:58 a.m.