Triple
T4231926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taylor & Francis journals |
E94598
|
entity |
| Predicate | hasArchivingPolicy |
P45347
|
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, hasArchivingPolicy, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchivingPolicy Context triple: [Taylor & Francis journals, hasArchivingPolicy, yes]
-
A.
archivePolicy
chosen
Indicates the rules or conditions governing how items are stored, retained, and managed in an archive.
-
B.
preservationPolicy
Indicates the rules or strategy governing how something is maintained, protected, and retained over time.
-
C.
archivesAccessPolicy
Indicates the rules or conditions governing who can access archives and under what circumstances.
-
D.
hasPolicyHistory
Indicates that an entity is associated with a record or sequence of past policies that have applied to it over time.
-
E.
hasReferencePolicy
Indicates that an entity is governed by or associated with a specific reference policy that defines how it should be used, accessed, or managed.
- 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.