Triple
T3720858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akedah |
E81633
|
entity |
| Predicate | refersToAction |
P51427
|
FINISHED |
| Object | binding of Isaac on the altar |
—
|
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: binding of Isaac on the altar | Statement: [Akedah, refersToAction, binding of Isaac on the altar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToAction Context triple: [Akedah, refersToAction, binding of Isaac on the altar]
-
A.
actsOn
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
B.
refersToRole
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
-
C.
refersSpecificallyTo
Indicates that one entity makes an explicit, precise reference to another particular entity, distinguishing it from more general or ambiguous references.
-
D.
canRefer
Indicates that one entity has the ability or permission to mention, point to, or direct attention to another entity.
-
E.
refersToAspect
Indicates that one entity specifically references or points to a particular aspect, feature, or component of another entity.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adca9b5ca8819094299fffc02606ce |
completed | March 8, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69adc0436e508190909ec4a3e8443aef |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc48ec1a081909af0ff9f267c0ffe |
completed | March 8, 2026, 6:48 p.m. |
Created at: March 8, 2026, 3:34 p.m.