Triple
T9936500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beverly Marsh |
E192771
|
entity |
| Predicate | overcomes |
P91239
|
FINISHED |
| Object | fear |
—
|
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: fear | Statement: [Beverly Marsh, overcomes, fear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overcomes Context triple: [Beverly Marsh, overcomes, fear]
-
A.
surpasses
Indicates that one entity exceeds or goes beyond another in degree, quality, performance, or achievement.
-
B.
overtook
Indicates that one entity moved past and ahead of another that was previously in front, typically while both were in motion.
-
C.
over
Indicates that one entity is positioned higher than and extending across or above another entity, often covering or spanning it.
-
D.
overcameHoldingOf
Indicates that one entity successfully defeated, reversed, or nullified another entity’s control, possession, or dominance over something.
-
E.
seeksToOvercome
Indicates an intentional effort by one entity to defeat, surpass, or remove an obstacle, limitation, or opposing force associated with another entity or condition.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5e3bfa88190a88f20f2687a2583 |
completed | April 2, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:44 p.m.