Triple
T2799629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .pw |
E53120
|
entity |
| Predicate | RFCCompliant |
P42399
|
FINISHED |
| Object | RFC 1591 |
—
|
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: RFC 1591 | Statement: [.pw, RFCCompliant, RFC 1591]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RFCCompliant Context triple: [.pw, RFCCompliant, RFC 1591]
-
A.
indicatesComplianceWith
chosen
Indicates that one entity conforms to, satisfies, or adheres to the rules, standards, or requirements specified by another entity or framework.
-
B.
OSIApproved
Indicates that a software license has been reviewed and approved by the Open Source Initiative (OSI) as complying with its Open Source Definition.
-
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.
deprecatedInRFC
Indicates that a specification, feature, or practice has been formally marked as deprecated within a particular RFC document.
-
E.
onStandardsTrack
Indicates that the subject is part of an officially recognized, actively developed standards process or pathway toward becoming a formal standard.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abddf31eec8190a898713e53d1aa5c |
completed | March 7, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69abdd040f9481908e9c7a2df88ea1ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.