Triple
T31582072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penuel |
E805851
|
entity |
| Predicate | connectedToName |
P197663
|
FINISHED |
| Object | Israel (as Jacob’s new name) |
—
|
NE NERFINISHED |
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: Israel (as Jacob’s new name) | Statement: [Penuel, connectedToName, Israel (as Jacob’s new name)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToName Context triple: [Penuel, connectedToName, Israel (as Jacob’s new name)]
-
A.
commonConnectorName
Indicates that two or more entities share the same connector name used to link or interface them.
-
B.
connectionTo
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
C.
connectsState
Indicates a relationship where one entity serves as a link or conduit between different states, conditions, or statuses of another entity.
-
D.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
E.
plannedToBeConnectedTo
Indicates that one entity is intended or scheduled to be linked or joined with another entity in the future.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
| PDg | Predicate description generation | batch_69fea1f4daa88190bd3cc1ace684e77f |
completed | May 9, 2026, 2:54 a.m. |
Created at: April 30, 2026, 10:24 p.m.