Triple
T13682454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boneh Yerushalayim |
E328034
|
entity |
| Predicate | variantIncludes |
P1393
|
FINISHED |
| Object | mention of Shabbat on Shabbat |
—
|
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: mention of Shabbat on Shabbat | Statement: [Boneh Yerushalayim, variantIncludes, mention of Shabbat on Shabbat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: variantIncludes Context triple: [Boneh Yerushalayim, variantIncludes, mention of Shabbat on Shabbat]
-
A.
includesMatch
Indicates that one entity contains or encompasses a particular match or matching instance of another entity.
-
B.
alsoContains
Indicates that something includes, in addition to its primary contents, another specified element or component.
-
C.
weakenedVariantsInclude
Indicates that a set of weakened or attenuated forms of something (e.g., a virus, argument, or feature) contains or encompasses the specified variant.
-
D.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
E.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc66e75188190a9e82fdc5eb26513 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.