Triple
T18370944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish Saturday schools |
E446177
|
entity |
| Predicate | typicalPupilsAgeRange |
P78715
|
FINISHED |
| Object | preschool children |
—
|
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: preschool children | Statement: [Polish Saturday schools, typicalPupilsAgeRange, preschool children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPupilsAgeRange Context triple: [Polish Saturday schools, typicalPupilsAgeRange, preschool children]
-
A.
acceptsPupilsFromAge
Indicates that an entity (such as a school or program) enrolls or admits pupils starting from a specified minimum age.
-
B.
typicalAge
Indicates the usual or characteristic age associated with an entity, event, or condition.
-
C.
typicalAgeRangeLower
chosen
Indicates the minimum age value that typically marks the lower bound of an expected or common age range for something.
-
D.
typicalLeavingAge
Indicates the age at which entities (such as people or groups) usually or most commonly leave a given context, place, or situation.
-
E.
primaryStudentAgeRange
Indicates the typical or required age range associated with primary-level students in a given context.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e5175324e48190a00572e15423feb7 |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:44 a.m.