Triple
T19977598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STAAR test |
E493731
|
entity |
| Predicate | hasPerformanceLevel |
P59739
|
FINISHED |
| Object | Did Not Meet Grade Level |
—
|
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: Did Not Meet Grade Level | Statement: [STAAR test, hasPerformanceLevel, Did Not Meet Grade Level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformanceLevel Context triple: [STAAR test, hasPerformanceLevel, Did Not Meet Grade Level]
-
A.
targetPerformanceLevel
Indicates the specific performance standard or level that an entity is expected or required to achieve.
-
B.
hasPerformanceElement
Indicates that one entity includes, contains, or is associated with a specific performance-related component or element.
-
C.
hasPerformanceLocation
Indicates that an event, performance, or show takes place at a specified location or venue.
-
D.
hasRatingLevel
chosen
Indicates that an entity is associated with a particular rating level or score category.
-
E.
achievementLevel
Indicates the degree or extent to which an entity has attained a particular goal, standard, or performance outcome.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d1054e08190993b92b86ec5bbc8 |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:27 p.m.