Triple
T14547657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uniform Resource Name |
E341329
|
entity |
| Predicate | usesScheme |
P114887
|
FINISHED |
| Object | urn |
—
|
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: urn | Statement: [Uniform Resource Name, usesScheme, urn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesScheme Context triple: [Uniform Resource Name, usesScheme, urn]
-
A.
hasScheme
Indicates that one entity is associated with, defined by, or governed through a particular scheme, plan, or structured framework.
-
B.
isUniqueWithinScheme
Indicates that an entity is the only one with its particular identifying characteristics within a given scheme or classification system.
-
C.
usesUpdateScheme
Indicates that one entity applies or operates according to a particular update scheme or updating method defined by another entity.
-
D.
hasCodeScheme
Indicates that something is associated with or organized according to a particular coding or classification scheme.
-
E.
notableScheme
Indicates that an entity is particularly recognized or prominent within a specific scheme, system, or organizational framework.
- F. None of above. chosen
Provenance (4 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb2ebdf9481909f4d2da1ad31099c |
completed | April 14, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de610330a48190b558235a14c0dc9f |
completed | April 14, 2026, 3:45 p.m. |
Created at: April 10, 2026, 1:23 a.m.