Triple
T13575133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tractate Beitzah |
E324261
|
entity |
| Predicate | hasOpeningTopic |
P60677
|
FINISHED |
| Object | egg laid on Yom Tov |
—
|
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: egg laid on Yom Tov | Statement: [Tractate Beitzah, hasOpeningTopic, egg laid on Yom Tov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpeningTopic Context triple: [Tractate Beitzah, hasOpeningTopic, egg laid on Yom Tov]
-
A.
hasOpening
Indicates that one entity possesses or features an opening, gap, or entrance that allows access, passage, or exposure.
-
B.
hasOpeningSetting
Indicates that one entity (typically a narrative work) has its initial scene or setting located in the other entity.
-
C.
hasOpeningType
Indicates that one entity has, features, or is characterized by a particular type or kind of opening.
-
D.
openingTopic
chosen
Indicates the primary subject or theme that initiates a discussion, conversation, or document.
-
E.
hasOpeningFeature
Indicates that an entity possesses a specific characteristic, element, or attribute related to its opening or entry point.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb02b1f108190a12af382d1de70bb |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.