Triple
T12633955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agunot |
E301710
|
entity |
| Predicate | requiresForResolution |
P83972
|
FINISHED |
| Object | deliveryOfValidGet |
—
|
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: deliveryOfValidGet | Statement: [Agunot, requiresForResolution, deliveryOfValidGet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresForResolution Context triple: [Agunot, requiresForResolution, deliveryOfValidGet]
-
A.
requiresForFeature
Indicates that one entity must be present, implemented, or satisfied in order for a particular feature of another entity to be available or function correctly.
-
B.
resolutionRequires
chosen
Indicates that resolving one issue, task, or condition depends on first completing or satisfying another specified prerequisite.
-
C.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
D.
requiresSources
Indicates that something must be supported, justified, or validated by one or more external sources.
-
E.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:15 p.m.