Triple
T20012101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helena |
E494612
|
entity |
| Predicate | influencesPlotBy |
P98526
|
FINISHED |
| Object | following Demetrius into the forest |
—
|
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: following Demetrius into the forest | Statement: [Helena, influencesPlotBy, following Demetrius into the forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influencesPlotBy Context triple: [Helena, influencesPlotBy, following Demetrius into the forest]
-
A.
influencesPlotOf
chosen
Indicates that one entity has an effect on or helps shape the storyline or narrative development of another entity.
-
B.
typeOfInfluence
Indicates the specific nature or category of influence that one entity exerts on another.
-
C.
influencesFocus
Indicates that one entity affects or shapes the attention, concentration, or focal priorities of another entity.
-
D.
exploresInfluence
Indicates that one entity investigates, examines, or analyzes the impact or effect that another entity has.
-
E.
designInfluenceOn
Indicates that one design, designer, or design-related factor has an effect on shaping, guiding, or altering another design or design outcome.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623773d88190826616a02d3c3e69 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:34 p.m.