Triple
T26395742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St John the Baptist Primary School, Fauldhouse |
E663546
|
entity |
| Predicate | typicalStartingAge |
P87250
|
FINISHED |
| Object | 4–5 |
—
|
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: 4–5 | Statement: [St John the Baptist Primary School, Fauldhouse, typicalStartingAge, 4–5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStartingAge Context triple: [St John the Baptist Primary School, Fauldhouse, typicalStartingAge, 4–5]
-
A.
typicalAge
Indicates the usual or characteristic age associated with an entity, event, or condition.
-
B.
approximateStartAge
chosen
Indicates the estimated or roughly determined age at which an event, condition, or state begins.
-
C.
typicalAgeRangeLower
Indicates the minimum age value that typically marks the lower bound of an expected or common age range for something.
-
D.
typicalEligibilityAge
Indicates the usual or standard age at which an entity qualifies for or becomes eligible for a particular status, benefit, or activity.
-
E.
typicallyIssuedAtAge
Indicates the age at which something is most commonly or customarily issued to an individual.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: April 26, 2026, 11:28 p.m.