Triple
T21465488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Auk |
E529583
|
entity |
| Predicate | hasPeerReviewedStatus |
P1388
|
FINISHED |
| Object | peer-reviewed |
—
|
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: peer-reviewed | Statement: [The Auk, hasPeerReviewedStatus, peer-reviewed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeerReviewedStatus Context triple: [The Auk, hasPeerReviewedStatus, peer-reviewed]
-
A.
peerReviewed
chosen
Indicates that a work, study, or submission has been evaluated and critiqued by qualified experts in the same field before acceptance or publication.
-
B.
hasPeerReviewPolicy
Indicates that an entity maintains or is governed by a specific policy outlining how peer review is conducted.
-
C.
hasCitationStatus
Indicates the current citation-related state or condition assigned to a referenced work or source (e.g., cited, uncited, pending, or deprecated).
-
D.
hasCommunityReviewForPublication
Indicates that a community has provided a review or evaluation for a specific publication.
-
E.
publicationStatus
Indicates the current state or phase of a work within its publication lifecycle, such as draft, under review, published, or retired.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9f1b3cc819092c200f09c6f461e |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:09 p.m.