Triple
T31582071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penuel |
E805851
|
entity |
| Predicate | centralFigureInNarrative |
P1183
|
FINISHED |
| Object | Jacob |
—
|
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: Jacob | Statement: [Penuel, centralFigureInNarrative, Jacob]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralFigureInNarrative Context triple: [Penuel, centralFigureInNarrative, Jacob]
-
A.
centralFigureTrait
Indicates that a particular trait or characteristic is associated with the central or primary figure in a given context.
-
B.
narrativelyCenteredIn
Indicates that an event, character, or element is positioned as the primary focus or organizing center of a narrative within a given context.
-
C.
hasCentralFigure
chosen
Indicates that something features a primary or most important figure at its core or focus.
-
D.
commandingFigureInStory
Indicates that one entity serves as a dominant, authoritative, or controlling figure within the narrative context of another entity’s story.
-
E.
centralFigureVenerated
Indicates that the subject is regarded and honored as a primary or focal object of reverence or worship by others.
- 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_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 30, 2026, 10:24 p.m.