Triple
T16748350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ClinicalKey |
E407011
|
entity |
| Predicate | publisherOfContent |
P1759
|
FINISHED |
| Object | Elsevier medical titles |
—
|
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: Elsevier medical titles | Statement: [ClinicalKey, publisherOfContent, Elsevier medical titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherOfContent Context triple: [ClinicalKey, publisherOfContent, Elsevier medical titles]
-
A.
publisherOfWorkAppearingIn
Indicates that an entity is the publisher responsible for issuing a work in which another specified work appears (e.g., as part of a collection, volume, or compilation).
-
B.
publisherType
Indicates the classification or category of a publisher in relation to a published work or entity.
-
C.
publishingOrganization
chosen
Indicates the organization responsible for issuing or making the referenced work publicly available.
-
D.
coPublisher
Indicates that two or more entities jointly publish the same work or content.
-
E.
hasPublisher
Indicates that an entity is published or issued by a specific publisher.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa2439848190a86a5bfc0702e2fe |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.