Triple
T15155145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taylor and Francis (historical firm) |
E362051
|
entity |
| Predicate | publishedForm |
P25668
|
FINISHED |
| Object | scholarly journals |
—
|
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: scholarly journals | Statement: [Taylor and Francis (historical firm), publishedForm, scholarly journals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishedForm Context triple: [Taylor and Francis (historical firm), publishedForm, scholarly journals]
-
A.
publishedAs
Indicates that an entity is released, issued, or made publicly available under a particular name, format, or identity.
-
B.
publishedDocument
Indicates that an entity has formally issued or made a document publicly available.
-
C.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
D.
publishedEdition
Indicates that one entity is a specific edition or version that has been formally published of another work or resource.
-
E.
publishingForm
chosen
Indicates the medium or format in which something is published or made publicly available.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0060b0cd08190afad14cffcc7d93f |
completed | April 15, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:08 a.m.