Triple
T17235269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lytton Park |
E418340
|
entity |
| Predicate | educationAccess |
P126490
|
FINISHED |
| Object | near quality public schools |
—
|
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: near quality public schools | Statement: [Lytton Park, educationAccess, near quality public schools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: educationAccess Context triple: [Lytton Park, educationAccess, near quality public schools]
-
A.
educationRight
Indicates that an entity holds a right or entitlement to receive education or educational opportunities.
-
B.
educationUse
Indicates the use or application of something specifically for educational purposes or in an educational context.
-
C.
educationProvision
Indicates the act or arrangement of supplying educational services, resources, or opportunities to individuals or groups.
-
D.
educationSetting
Indicates the type or context of the educational environment in which the related entity participates or operates.
-
E.
educationSystem
Indicates the relationship in which an entity is part of, governed by, or operates within a particular system or structure of education.
- F. None of above. chosen
Provenance (4 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dfb04e481909f4ee3ed31fffe10 |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:39 a.m.