Triple
T19160381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standards of Learning tests |
E469036
|
entity |
| Predicate | resultUsedBy |
P64275
|
FINISHED |
| Object | state policymakers in Virginia |
—
|
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: state policymakers in Virginia | Statement: [Standards of Learning tests, resultUsedBy, state policymakers in Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultUsedBy Context triple: [Standards of Learning tests, resultUsedBy, state policymakers in Virginia]
-
A.
resultUsage
Indicates how the outcome or result of an action, process, or event is used, applied, or consumed in relation to another entity or context.
-
B.
outputUsedBy
chosen
Indicates that a particular output produced by one entity is consumed, referenced, or otherwise utilized by another entity.
-
C.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
-
D.
laterUsedBy
Indicates that something is subsequently utilized or employed by a specified entity at a later time.
-
E.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eebc52dc819085666dbbeea365a6 |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.