Triple
T21422746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nona |
E528475
|
entity |
| Predicate | temporalAspectOfFate |
P29111
|
FINISHED |
| Object | past and beginning |
—
|
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 and beginning | Statement: [Nona, temporalAspectOfFate, past and beginning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalAspectOfFate Context triple: [Nona, temporalAspectOfFate, past and beginning]
-
A.
eventualFate
Indicates the ultimate outcome or final state that an entity is destined to reach over time.
-
B.
temporalAspect
chosen
Indicates the time-related characteristics or phase (such as duration, frequency, or temporal status) associated with an event or relationship.
-
C.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
D.
viewOnFate
Indicates a relationship where one entity holds a particular belief, attitude, or perspective about fate or predestination.
-
E.
altersFateOf
Indicates that one entity changes, redirects, or otherwise influences the destined outcome or future course of another entity.
- 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee8139ce848190b812d6d07f1bdef8 |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:48 p.m.