Triple
T12325102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLEP exams |
E293808
|
entity |
| Predicate | typicalPassingScore |
P15617
|
FINISHED |
| Object | 50 on the CLEP 20–80 scale |
—
|
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: 50 on the CLEP 20–80 scale | Statement: [CLEP exams, typicalPassingScore, 50 on the CLEP 20–80 scale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPassingScore Context triple: [CLEP exams, typicalPassingScore, 50 on the CLEP 20–80 scale]
-
A.
requiresMinimumScore
Indicates that one entity can only be obtained, accessed, or considered valid if another entity’s score meets or exceeds a specified minimum threshold.
-
B.
gradingSystem
Indicates the method or criteria by which performance, quality, or achievement is evaluated and assigned a grade or score.
-
C.
isScoreFor
chosen
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
D.
gradeWithin
Indicates that one value’s grade or level falls within a specified range or interval relative to another.
-
E.
typicalGradesInclude
Indicates that a set of commonly expected or standard grades for something contains the specified grade or grades.
- 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec5be788190b82d2edc6a0f1095 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.