Triple
T252337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts Comprehensive Assessment System |
E5175
|
entity |
| Predicate | dataUsedBy |
P7412
|
FINISHED |
| Object | Massachusetts school districts |
—
|
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: Massachusetts school districts | Statement: [Massachusetts Comprehensive Assessment System, dataUsedBy, Massachusetts school districts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataUsedBy Context triple: [Massachusetts Comprehensive Assessment System, dataUsedBy, Massachusetts school districts]
-
A.
dataUse
Indicates how data is intended to be accessed, processed, or applied within a particular context or activity.
-
B.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
C.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
D.
dataUsers
chosen
Indicates a relationship where certain entities use, access, or consume specific data.
-
E.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d39eb3881909f435043c8697f13 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b678d6c81909780e1995c1ca691 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.