Triple
T4231929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taylor & Francis journals |
E94598
|
entity |
| Predicate | hasPublicationEthicsPolicy |
P10803
|
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: [Taylor & Francis journals, hasPublicationEthicsPolicy, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicationEthicsPolicy Context triple: [Taylor & Francis journals, hasPublicationEthicsPolicy, yes]
-
A.
hasPeerReviewPolicy
Indicates that an entity maintains or is governed by a specific policy outlining how peer review is conducted.
-
B.
hasEthicsDocument
chosen
Indicates that an entity possesses or is associated with a formal document outlining ethical principles, guidelines, or policies.
-
C.
hasEthicsBody
Indicates that an entity is associated with, overseen by, or governed through a formal ethics committee or ethics review body.
-
D.
isScholarly
Indicates that an entity exhibits characteristics of academic rigor, research-based inquiry, and adherence to scholarly standards or conventions.
-
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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e642aac8190977dd101e27afcbb |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.