Triple
T12934210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montclair College Preparatory School |
E309461
|
entity |
| Predicate | servedLevel |
P93618
|
FINISHED |
| Object | grades 9–12 |
—
|
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: grades 9–12 | Statement: [Montclair College Preparatory School, servedLevel, grades 9–12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedLevel Context triple: [Montclair College Preparatory School, servedLevel, grades 9–12]
-
A.
levelServed
chosen
Indicates that a particular service, function, or resource is provided or made available at a specified level or tier.
-
B.
servesSkillLevel
Indicates that one entity provides or is appropriate for a particular level of skill in another entity.
-
C.
lowerLevelServes
Indicates that a lower-level component, service, or entity provides functionality or support to a higher-level component, service, or entity.
-
D.
served
Indicates that one entity provided a service, assistance, or role-based function to or for another entity.
-
E.
serviceLevel
Indicates the degree or quality of service provided or received in the relationship between entities.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:42 p.m.