Triple
T200457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Journal Interface |
E4093
|
entity |
| Predicate | peerReviewProcess |
P630
|
FINISHED |
| Object | external expert review |
—
|
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: external expert review | Statement: [Journal Interface, peerReviewProcess, external expert review]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peerReviewProcess Context triple: [Journal Interface, peerReviewProcess, external expert review]
-
A.
peerReview
chosen
Indicates that one entity evaluates, critiques, or validates the work or performance of another entity, typically as an equal in expertise or status.
-
B.
editorialProcess
Indicates the process by which content is reviewed, revised, and approved before publication or release.
-
C.
peerReviewed
Indicates that a work, study, or submission has been evaluated and critiqued by qualified experts in the same field before acceptance or publication.
-
D.
reviewedBy
Indicates that an item, work, or action has been examined and evaluated by a specific agent or reviewer.
-
E.
hasEditorialBoard
Indicates that an entity (such as a publication or journal) is overseen or governed by a specific editorial board.
- 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_69a254bca59881909a15e1496f1508c7 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25c2ead8481909996042efcae5e9d |
completed | Feb. 28, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69a25b4a0d448190a6fa6aeb30dc7e13 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:44 a.m.