Triple
T2964126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israel |
E80119
|
entity |
| Predicate | nameChangeEvent |
P45259
|
FINISHED |
| Object | Jacob renamed Israel after wrestling with a divine being |
—
|
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: Jacob renamed Israel after wrestling with a divine being | Statement: [Israel, nameChangeEvent, Jacob renamed Israel after wrestling with a divine being]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameChangeEvent Context triple: [Israel, nameChangeEvent, Jacob renamed Israel after wrestling with a divine being]
-
A.
changedNameIn
Indicates that an entity has altered or adopted a different name within a specific context, time period, or jurisdiction.
-
B.
nameChangeReason
Indicates the reason or justification for a change in an entity’s name.
-
C.
nameChangeDate
Indicates the date on which an entity’s name was officially changed.
-
D.
changedSurnameFrom
Indicates that an entity has adopted a new surname that was previously a different, specified surname.
-
E.
nameChosenToBe
Indicates that an entity has been given or selected to have a particular name.
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9958b1e48190a77f37bf63333c5b |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad98379fac8190a4dfe530787703c9 |
completed | March 8, 2026, 3:39 p.m. |
Created at: March 8, 2026, 2:58 p.m.