Triple
T21013195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Assessment of Student Performance and Progress |
E517602
|
entity |
| Predicate | hasScoreScale |
P16725
|
FINISHED |
| Object | performance levels |
—
|
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: performance levels | Statement: [California Assessment of Student Performance and Progress, hasScoreScale, performance levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScoreScale Context triple: [California Assessment of Student Performance and Progress, hasScoreScale, performance levels]
-
A.
scoreScale
chosen
Indicates the scale or range on which a score or rating is expressed or measured.
-
B.
hasScoreSystem
Indicates that an entity uses, is governed by, or is associated with a particular scoring or rating system.
-
C.
hasScoreCharacteristic
Indicates that one entity possesses or is associated with a particular scoring-related characteristic or property.
-
D.
hasScoreType
Indicates that an entity is associated with a particular type or category of score.
-
E.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
- 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc41d57881908b9ab17d1844a8d0 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:53 p.m.