Triple
T8755977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 8259 |
E208072
|
entity |
| Predicate | documentURI |
P47307
|
FINISHED |
| Object | https://www.rfc-editor.org/rfc/rfc8259 |
—
|
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: https://www.rfc-editor.org/rfc/rfc8259 | Statement: [RFC 8259, documentURI, https://www.rfc-editor.org/rfc/rfc8259]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentURI Context triple: [RFC 8259, documentURI, https://www.rfc-editor.org/rfc/rfc8259]
-
A.
documentSource
Indicates that one entity serves as the origin, provider, or provenance source for a given document.
-
B.
namespaceURI
Indicates the URI that defines the namespace to which a given identifier, element, or resource belongs.
-
C.
hasReferenceURL
chosen
Indicates that an entity is associated with a specific web address that serves as a reference or source of additional information about it.
-
D.
locationInDocument
Indicates that one entity specifies where another entity is situated or referenced within a document.
-
E.
documentLeak
Indicates that a document has been disclosed or exposed to unauthorized parties, typically without permission or intended confidentiality.
- 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5dd95e9481909cc88e8d91601754 |
completed | March 31, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:40 p.m.