Triple
T26495048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungry generation |
E669257
|
entity |
| Predicate | movementPublication |
P161017
|
FINISHED |
| Object | little magazines |
—
|
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: little magazines | Statement: [Hungry generation, movementPublication, little magazines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementPublication Context triple: [Hungry generation, movementPublication, little magazines]
-
A.
movementPublication
chosen
Indicates a relationship where a publication is produced by, documents, or is otherwise associated with a particular movement.
-
B.
movementDocumented
Indicates that the movement or transfer of an entity from one place or state to another has been formally recorded or documented.
-
C.
movementProduction
Indicates a relationship where an entity generates, initiates, or causes physical movement or motion.
-
D.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
E.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 1:07 a.m.