Triple
T22814425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flipgrid |
E565062
|
entity |
| Predicate | supportsAssessmentType |
P24486
|
FINISHED |
| Object | formative assessment |
—
|
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: formative assessment | Statement: [Flipgrid, supportsAssessmentType, formative assessment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAssessmentType Context triple: [Flipgrid, supportsAssessmentType, formative assessment]
-
A.
supportsTestType
Indicates that one entity is capable of handling, executing, or being compatible with a specified type of test.
-
B.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
C.
supportsProgramType
Indicates that one entity is capable of handling, offering, or being compatible with a specified type of program.
-
D.
typeOfAssessmentAlignment
Indicates that an assessment is aligned with, or corresponds to, a particular standard, objective, or framework.
-
E.
supportsModelType
Indicates that an entity is compatible with, or can operate using, a specified model type.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d62b0ec8190ac22909192e8a876 |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:33 p.m.