Triple
T1269654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mishneh Torah |
E15679
|
entity |
| Predicate | deniesNeedFor |
P6844
|
FINISHED |
| Object | Talmudic source citations in the code itself |
—
|
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: Talmudic source citations in the code itself | Statement: [Mishneh Torah, deniesNeedFor, Talmudic source citations in the code itself]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deniesNeedFor Context triple: [Mishneh Torah, deniesNeedFor, Talmudic source citations in the code itself]
-
A.
recognizedNeedFor
Indicates that one entity has identified or acknowledged the necessity or requirement for another entity or condition.
-
B.
typicallyDenies
Indicates that an entity, in most usual or common circumstances, refuses, rejects, or does not grant something to another entity.
-
C.
needBased
Indicates that something is determined, allocated, or provided according to the level of need rather than uniform or fixed criteria.
-
D.
isNotRequiredFor
chosen
Indicates that one entity is not necessary or mandatory for the existence, occurrence, validity, or completion of another entity or process.
-
E.
requiresAbstentionFrom
Indicates that one entity imposes or necessitates refraining from a specific action, behavior, or substance by another 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c03aaa8c8190bacb7de5a38329da |
completed | March 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.