Triple
T24135234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir Yeshiva |
E598063
|
entity |
| Predicate | dailySchedule |
P3309
|
FINISHED |
| Object | intensive study from early morning to late night |
—
|
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: intensive study from early morning to late night | Statement: [Mir Yeshiva, dailySchedule, intensive study from early morning to late night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dailySchedule Context triple: [Mir Yeshiva, dailySchedule, intensive study from early morning to late night]
-
A.
dailyPractice
Indicates a recurring action or behavior that is performed every day as a regular practice or routine.
-
B.
typicalSchedule
chosen
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
C.
dailyCycle
Indicates a recurring pattern or process that happens once every day as part of a regular cycle.
-
D.
dayType
Indicates the classification or category of a given day based on its characteristics or role (e.g., weekday, weekend, holiday).
-
E.
dayUse
Indicates that something is intended or permitted to be used during the daytime.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7c3ce08190bcbd9056a6630c2f |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:26 p.m.