Triple
T35345412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiddushei Rabbi Akiva Eiger |
E1020725
|
entity |
| Predicate | includedAlongside |
P16605
|
FINISHED |
| Object | standard Talmud commentaries |
—
|
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: standard Talmud commentaries | Statement: [Chiddushei Rabbi Akiva Eiger, includedAlongside, standard Talmud commentaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedAlongside Context triple: [Chiddushei Rabbi Akiva Eiger, includedAlongside, standard Talmud commentaries]
-
A.
includedWith
chosen
Indicates that one entity is provided or packaged together as part of another entity.
-
B.
includedBy
Indicates that one entity is contained within, encompassed by, or treated as a subset or member of another entity.
-
C.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
D.
includedSingle
Indicates that one specific, individual item is contained within or made part of another set, group, or collection.
-
E.
includedPass
Indicates that one entity’s pass or access credential is contained within, covered by, or granted through 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.