Triple
T32498704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multipurpose Internet Mail Extensions |
E830592
|
entity |
| Predicate | originalRFC |
—
|
GENERATED |
| Object | RFC 1341 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalRFC Context triple: [Multipurpose Internet Mail Extensions, originalRFC, RFC 1341]
-
A.
originalRfc
chosen
Indicates that something is the initial or authoritative RFC (Request for Comments) document from which a specification, standard, or later revision originates.
-
B.
originalSubject
Indicates that the entity is the initial or primary subject associated with an event, statement, or relation, before any changes, transformations, or reassignments occur.
-
C.
hasRFC
Indicates that an entity is associated with, described by, or defined in a specific RFC (Request for Comments) document.
-
D.
originalText
Indicates that one text is the initial, unmodified version from which other versions, translations, or representations are derived.
-
E.
originalFor
Indicates that one entity serves as the source, basis, or prototype from which another entity is derived, adapted, or created.
- F. None of above.
Provenance (1 batch)
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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:59 a.m.