Triple
T19077815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Promise of Isaac |
E466948
|
entity |
| Predicate | fulfilledIn |
P108444
|
FINISHED |
| Object | birth of Isaac |
—
|
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: birth of Isaac | Statement: [Promise of Isaac, fulfilledIn, birth of Isaac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fulfilledIn Context triple: [Promise of Isaac, fulfilledIn, birth of Isaac]
-
A.
fulfilledVow
chosen
Indicates that an entity has carried out or honored a previously made vow or promise.
-
B.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
C.
ultimateFulfillmentAt
Indicates that something reaches its highest or final state of completion, satisfaction, or realization at a specified point, place, or condition.
-
D.
concludedAfter
Indicates that one event or process finishes at a time later than the completion of another event or process.
-
E.
completedBy
Indicates that a task, process, or action has been finished or carried out by a particular entity.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e5591081908a4f8e4b2011b408 |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.