Triple
T8455947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Progressive Writers Movement |
E199917
|
entity |
| Predicate | literaryApproach |
P16928
|
FINISHED |
| Object | radical writing |
—
|
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: radical writing | Statement: [Progressive Writers Movement, literaryApproach, radical writing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryApproach Context triple: [Progressive Writers Movement, literaryApproach, radical writing]
-
A.
literaryLanguage
Indicates that an entity is expressed, written, or communicated using a particular literary or standardized written language.
-
B.
literarySubject
Indicates that one entity serves as the subject, topic, or focus of a literary work created by another entity.
-
C.
literaryFeature
chosen
Indicates a relationship where something possesses or exhibits a characteristic, device, or stylistic element used in literature.
-
D.
literaryPurpose
Indicates the intended function, effect, or communicative goal that a text or passage is meant to achieve within a literary context.
-
E.
literaryInterest
Indicates that one entity has an interest in, appreciation of, or engagement with the literary works or writings of another entity.
- 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_69ca8318231881908fd1bc1c4d45d286 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe48e0ae481908b40f7f124b0551e |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.