Triple
T3093865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3710 |
E64545
|
entity |
| Predicate | hasURI |
P19706
|
FINISHED |
| Object | https://www.rfc-editor.org/rfc/rfc3710 |
—
|
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/rfc3710 | Statement: [RFC 3710, hasURI, https://www.rfc-editor.org/rfc/rfc3710]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasURI Context triple: [RFC 3710, hasURI, https://www.rfc-editor.org/rfc/rfc3710]
-
A.
namespaceURI
Indicates the URI that defines the namespace to which a given identifier, element, or resource belongs.
-
B.
hasCanonicalReference
Indicates that one entity serves as the authoritative or standard reference source for another entity.
-
C.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
D.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
E.
typicalURIForm
chosen
Indicates that one entity is the standard or canonical URI form typically used to represent 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada23876a4819095bfc28640d8c200 |
completed | March 8, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ad9ded78f881908be6fc0fb7c35764 |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:03 p.m.