Triple
T21085825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngembak Geni |
E519483
|
entity |
| Predicate | followsEventType |
P101970
|
FINISHED |
| Object | day of silence and self-reflection |
—
|
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: day of silence and self-reflection | Statement: [Ngembak Geni, followsEventType, day of silence and self-reflection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsEventType Context triple: [Ngembak Geni, followsEventType, day of silence and self-reflection]
-
A.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
B.
followerEvent
Indicates that one entity begins or performs the action of following another entity, typically recorded as a discrete event in time.
-
C.
associatedEventType
Indicates that one entity is linked to another by the type or category of event with which it is associated.
-
D.
refersToEventType
chosen
Indicates that one entity references or is associated with a specific type or category of event.
-
E.
followsCalendarOf
Indicates that one entity adopts and adheres to the scheduling, events, or time structure defined by another entity’s calendar.
- 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094ad1c08190a4b9d2668a6362b2 |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:50 p.m.