Triple
T31582058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penuel |
E805851
|
entity |
| Predicate | afterEventJacobSaid |
P1691
|
FINISHED |
| Object | I have seen God face to face |
—
|
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: I have seen God face to face | Statement: [Penuel, afterEventJacobSaid, I have seen God face to face]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterEventJacobSaid Context triple: [Penuel, afterEventJacobSaid, I have seen God face to face]
-
A.
aftermathOf
Indicates that one event, state, or condition occurs as a consequence or result following another event.
-
B.
aftermathActivity
Indicates the activity or state that occurs as a direct consequence of, or in response to, a preceding event or situation.
-
C.
hadEvent
Indicates that an entity experienced, hosted, or was associated with a specific event at some point in time.
-
D.
closedAfterEvent
Indicates that an entity becomes or is marked as closed following the occurrence of a specified event.
-
E.
after
chosen
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 30, 2026, 10:24 p.m.