Triple
T22375537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | vCard |
E553142
|
entity |
| Predicate | introducedInRFC |
P5655
|
FINISHED |
| Object | RFC 2426 |
—
|
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 2426 | Statement: [vCard, introducedInRFC, RFC 2426]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2426 Context triple: [vCard, introducedInRFC, RFC 2426]
-
A.
RFC 2426
chosen
RFC 2426 is the Internet standards document that specifies the vCard electronic business card format used for representing and exchanging personal contact information.
-
B.
RFC 2236
RFC 2236 is the Internet Engineering Task Force (IETF) specification that defines version 2 of the Internet Group Management Protocol (IGMPv2) used for managing IPv4 multicast group memberships.
-
C.
RFC 4512
RFC 4512 is an IETF specification that defines the core models, schema, and protocol elements for the Lightweight Directory Access Protocol (LDAP) version 3.
-
D.
RFC 2427
RFC 2427 is an IETF standard that specifies how to encapsulate multiple network layer protocols over Frame Relay networks.
-
E.
RFC 2254
RFC 2254 is an earlier Internet standard that defined the string representation of LDAP search filters before being superseded by RFC 4515.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedInRFC Context triple: [vCard, introducedInRFC, RFC 2426]
-
A.
introducedInStandard
chosen
Indicates that something (such as a concept, feature, or element) was first defined or formally specified in a particular standard.
-
B.
hasRFC
Indicates that an entity is associated with, described by, or defined in a specific RFC (Request for Comments) document.
-
C.
deprecatedInRFC
Indicates that a specification, feature, or practice has been formally marked as deprecated within a particular RFC document.
-
D.
originalRfc
Indicates that something is the initial or authoritative RFC (Request for Comments) document from which a specification, standard, or later revision originates.
-
E.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by another entity.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15807cb748190abd9adc08ca1ad4f |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.