Triple
T19244540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Placement |
E481213
|
entity |
| Predicate | typicalPassingScoreForCredit |
P22279
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Advanced Placement, typicalPassingScoreForCredit, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPassingScoreForCredit Context triple: [Advanced Placement, typicalPassingScoreForCredit, 3]
-
A.
requiresMinimumScore
chosen
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.
hasMaximumGrade
Indicates that an entity possesses the highest possible grade or score within a defined grading or evaluation system.
-
D.
typicalCreditRequirement
Indicates the usual or standard amount of credit that is generally required or expected in a given context.
-
E.
passFailBasis
Indicates that an outcome, evaluation, or decision is determined solely on a pass-or-fail basis rather than using a graded or ranked scale.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faf47820819081e8b6af852bb1dd |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:27 p.m.