Triple
T27598431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Non ti muovere |
E699964
|
entity |
| Predicate | protagonistConfronts |
P163504
|
FINISHED |
| Object | past affair |
—
|
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: past affair | Statement: [Non ti muovere, protagonistConfronts, past affair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistConfronts Context triple: [Non ti muovere, protagonistConfronts, past affair]
-
A.
helpsCharacterConfront
Indicates that one character actively supports or enables another character in facing and dealing with a difficult issue, fear, or challenge.
-
B.
protagonistAction
Indicates that the referenced entity performs the central or primary action associated with the main character in a narrative or scenario.
-
C.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
D.
protagonistReaction
Indicates how a main character responds emotionally or behaviorally to a particular event, situation, or stimulus.
-
E.
protagonistJoins
Indicates that a protagonist becomes a member of, or aligns themselves with, a particular group, organization, or cause.
- F. None of above. chosen
Provenance (4 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6397b64f881909d811225e57aac5e |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 2:07 p.m.