Triple
T16074651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oneworld Publications |
E389951
|
entity |
| Predicate | hasPublishingFocus |
P121788
|
FINISHED |
| Object | philosophy |
—
|
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: philosophy | Statement: [Oneworld Publications, hasPublishingFocus, philosophy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublishingFocus Context triple: [Oneworld Publications, hasPublishingFocus, philosophy]
-
A.
hasEditorialFocus
Indicates that an entity (such as a publication or section) is primarily concerned with or oriented around a particular editorial topic, theme, or subject area.
-
B.
hasPublishingProgram
Indicates that an entity operates or maintains a formal program or initiative for publishing content, works, or materials.
-
C.
hasPub
Indicates that an entity is associated with, or has access to, a public house (pub) as a related establishment or feature.
-
D.
hasPublisher
Indicates that an entity is published or issued by a specific publisher.
-
E.
hasPublishingFormat
Indicates that an entity is associated with a specific format or medium in which it is published or made publicly available.
- F. None of above. chosen
Provenance (4 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e1ff5cd7e481908a29214139a3de2e |
completed | April 17, 2026, 9:37 a.m. |
Created at: April 10, 2026, 4:57 a.m.