Triple
T672392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microbiology Resource Announcements |
E12999
|
entity |
| Predicate | hasDigitalArchivingPolicy |
P12561
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Microbiology Resource Announcements, hasDigitalArchivingPolicy, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigitalArchivingPolicy Context triple: [Microbiology Resource Announcements, hasDigitalArchivingPolicy, yes]
-
A.
hasDigitalArchive
Indicates that an entity maintains or is associated with a collection of materials stored in a digital archive.
-
B.
hasDigitalCollections
Indicates that an entity possesses or provides access to one or more collections of materials in digital form.
-
C.
hasDigitalLibrary
Indicates that an entity maintains or provides access to a collection of digital resources or publications.
-
D.
preservationPolicy
chosen
Indicates the rules or strategy governing how something is maintained, protected, and retained over time.
-
E.
hasDigitalForm
Indicates that something exists or is available in a digital or electronic format.
- 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a1b3682c8190a9b9a454480c3446 |
completed | March 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69a49d1a16c48190af89e3b078a4957e |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.