Triple
T30212789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ocean Press |
E768115
|
entity |
| Predicate | publishesTheme |
P181194
|
FINISHED |
| Object | revolutionary movements |
—
|
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: revolutionary movements | Statement: [Ocean Press, publishesTheme, revolutionary movements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishesTheme Context triple: [Ocean Press, publishesTheme, revolutionary movements]
-
A.
promotedTheme
chosen
Indicates that one entity actively highlights, advertises, or gives special emphasis to a particular theme or topic.
-
B.
impliesTheme
Indicates that one entity conceptually suggests, hints at, or leads to the thematic presence of another entity.
-
C.
editorialTheme
Indicates a relationship where an editorial work is associated with a specific overarching theme or subject focus that guides its content and presentation.
-
D.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
E.
transformationTheme
Indicates a thematic relationship in which one entity centers on or explores the process, experience, or idea of transformation in another.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: April 29, 2026, 7:33 p.m.