Triple
T22074859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Youth Test |
E545496
|
entity |
| Predicate | lunchBreak |
P56828
|
FINISHED |
| Object | scheduled mid-day break |
—
|
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: scheduled mid-day break | Statement: [Youth Test, lunchBreak, scheduled mid-day break]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lunchBreak Context triple: [Youth Test, lunchBreak, scheduled mid-day break]
-
A.
lunchBreakStartLocal
Indicates the local date and time at which a person's lunch break begins.
-
B.
mealPeriod
Indicates the time-of-day category (such as breakfast, lunch, or dinner) during which a meal or food-related event occurs.
-
C.
breakType
chosen
Indicates the specific kind or category of break or interruption that occurs in a process, activity, or sequence.
-
D.
break
Indicates that one entity causes another entity to separate into pieces, stop functioning, or otherwise lose its normal integrity or continuity.
-
E.
budbreak
Indicates the point in time or condition under which buds on a plant begin to open and resume active growth.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128b1904881909a1769ce8be39e05 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.