Triple
T12773672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godfrey Cass |
E305312
|
entity |
| Predicate | turningPointEvent |
P676
|
FINISHED |
| Object | revelation as Eppie’s biological father |
—
|
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: revelation as Eppie’s biological father | Statement: [Godfrey Cass, turningPointEvent, revelation as Eppie’s biological father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turningPointEvent Context triple: [Godfrey Cass, turningPointEvent, revelation as Eppie’s biological father]
-
A.
turningPointIn
chosen
Indicates that an event or situation serves as a decisive change or pivotal moment within a larger process, narrative, or development.
-
B.
turningPointAgainst
Indicates a pivotal moment or event that shifts momentum or advantage against a particular entity or side.
-
C.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
D.
peakEvent
Indicates the occurrence of a maximum or most intense point within a process, activity, or measurable phenomenon.
-
E.
significantEventEnd
Indicates the point in time when a significant event or occurrence comes to a close or is considered finished.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96df5b68481908a5d40516b09be52 |
completed | April 10, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:28 p.m.