Triple
T34158715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 8179 |
E876213
|
entity |
| Predicate | hasUrl |
P47307
|
FINISHED |
| Object | https://www.rfc-editor.org/rfc/rfc8179 |
—
|
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/rfc8179 | Statement: [RFC 8179, hasUrl, https://www.rfc-editor.org/rfc/rfc8179]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUrl Context triple: [RFC 8179, hasUrl, https://www.rfc-editor.org/rfc/rfc8179]
-
A.
hadURL
Indicates that an entity was associated with or linked to a specific URL at some point in time.
-
B.
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.
-
C.
hasPrimaryURL
Indicates that an entity is associated with its main or canonical web address (URL).
-
D.
hasExternalLink
Indicates that an entity is associated with a hyperlink pointing to a resource outside the current system or domain.
-
E.
hasAccessURL
Indicates that an entity is associated with a specific URL through which it can be accessed or retrieved.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fdedf708190ab68c2d567e086d0 |
completed | May 3, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.