Triple
T34666847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arba Minim |
E890279
|
entity |
| Predicate | legalDiscussionIn |
P195468
|
FINISHED |
| Object | Mishnah Sukkah |
—
|
NE NERFINISHED |
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: Mishnah Sukkah | Statement: [Arba Minim, legalDiscussionIn, Mishnah Sukkah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalDiscussionIn Context triple: [Arba Minim, legalDiscussionIn, Mishnah Sukkah]
-
A.
legalForum
Indicates the official legal venue or jurisdiction in which a dispute, case, or legal matter is to be heard or resolved.
-
B.
legalMatters
Indicates that one entity is involved with, concerned about, or responsible for legal issues, processes, or obligations related to another entity or context.
-
C.
hasLegalDiscussionIn
chosen
Indicates that a legal discussion or proceeding involving an entity takes place within a specified location or context.
-
D.
legalQuestion
Indicates that one entity poses or represents a question concerning legal rights, obligations, or interpretations to another entity or within a legal context.
-
E.
legalView
Indicates that one entity holds or expresses a legal opinion, interpretation, or judgment about another entity or situation.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff70ecc1a481909571b18d56d982b8 |
completed | May 9, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69ff70322a3c8190837840ea42cd3093 |
completed | May 9, 2026, 5:34 p.m. |
Created at: May 1, 2026, 2:05 a.m.