Triple
T17586126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La terra trema |
E428325
|
entity |
| Predicate | hasSequelPlan |
P25727
|
FINISHED |
| Object | intended trilogy about the working class |
—
|
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: intended trilogy about the working class | Statement: [La terra trema, hasSequelPlan, intended trilogy about the working class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSequelPlan Context triple: [La terra trema, hasSequelPlan, intended trilogy about the working class]
-
A.
hasSequelInDevelopment
chosen
Indicates that a work has a follow-up installment currently being planned, produced, or otherwise developed but not yet released.
-
B.
hasSequel
Indicates that one work is followed by another work that continues its story, timeline, or thematic development.
-
C.
hasSequelPotential
Indicates that a work or story has qualities suggesting it could be continued or expanded in a subsequent installment.
-
D.
hasSequelRumors
Indicates that there are rumors or unconfirmed reports suggesting a sequel exists or may be produced for the referenced work.
-
E.
hasSequelType
Indicates that one work has a sequel of a specified type or category in relation to another work.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e463d22f908190ae0f1eeafbe54459 |
completed | April 19, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.