Triple
T16747399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DOI |
E406990
|
entity |
| Predicate | typicalURLForm |
P19706
|
FINISHED |
| Object | https://doi.org/DOI |
—
|
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://doi.org/DOI | Statement: [DOI, typicalURLForm, https://doi.org/DOI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalURLForm Context triple: [DOI, typicalURLForm, https://doi.org/DOI]
-
A.
typicalURIForm
chosen
Indicates that one entity is the standard or canonical URI form typically used to represent another entity.
-
B.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
-
C.
nativeForm
Indicates that one entity is the original or native linguistic form of another, such as a word’s form in its source language.
-
D.
typicalLabelForm
Indicates that one label represents the standard or most commonly used form among multiple possible labels for the same entity or concept.
-
E.
typicalScriptForm
Indicates the usual or standard written script or notation in which something is commonly represented.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa2439848190a86a5bfc0702e2fe |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.