Triple
T27582522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4918 |
E699617
|
entity |
| Predicate | definesURINamespace |
P15686
|
FINISHED |
| Object | DAV: |
—
|
NE NERFINISHED |
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: DAV: | Statement: [RFC 4918, definesURINamespace, DAV:]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesURINamespace Context triple: [RFC 4918, definesURINamespace, DAV:]
-
A.
namespaceURI
chosen
Indicates the URI that defines the namespace to which a given identifier, element, or resource belongs.
-
B.
namedSpace
Indicates that an entity has been assigned or is associated with a specific name within a particular namespace or naming context.
-
C.
codeNamespace
Indicates the namespace or modular grouping in which a piece of code or programming element is defined.
-
D.
baseNamespace
Indicates the foundational namespace from which other namespaces, identifiers, or resources are defined or derived.
-
E.
usesURI
Indicates that one entity employs or references another entity via a specific Uniform Resource Identifier (URI) as its means of identification or access.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 27, 2026, 2:03 p.m.