Triple
T14803014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Thanks |
E347956
|
entity |
| Predicate | reasonForSelfPublication |
P24455
|
FINISHED |
| Object | rejection by numerous publishers |
—
|
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: rejection by numerous publishers | Statement: [No Thanks, reasonForSelfPublication, rejection by numerous publishers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForSelfPublication Context triple: [No Thanks, reasonForSelfPublication, rejection by numerous publishers]
-
A.
selfPublished
Indicates that an entity has published its own work independently, without an external publisher.
-
B.
publishingPurpose
chosen
Indicates the intended goal or reason for which something is being published.
-
C.
mayPublish
Indicates that an entity has the permission or authorization to publish another entity or piece of content.
-
D.
publishesFor
Indicates that one entity issues, releases, or makes content publicly available on behalf of, or in service of, another entity.
-
E.
reasonForPassage
Indicates the underlying cause, motivation, or purpose that explains why a particular passage or movement occurred.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decf30d044819082ac038e06481aab |
completed | April 14, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:34 a.m.