Triple
T2714343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | College Board |
E59932
|
entity |
| Predicate | testScoresUsedFor |
P33238
|
FINISHED |
| Object | college admissions |
—
|
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: college admissions | Statement: [College Board, testScoresUsedFor, college admissions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testScoresUsedFor Context triple: [College Board, testScoresUsedFor, college admissions]
-
A.
scoreUsedFor
chosen
Indicates that a particular score or rating is used for a specific purpose, decision, or downstream process.
-
B.
testTriesScored
Indicates that an entity scored a certain number of tries in a test (rugby) match.
-
C.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
D.
isUsedToTest
Indicates that one entity serves as a means or tool for evaluating, examining, or verifying another entity.
-
E.
usedInScoreGraphics
Indicates that something (such as a technique, element, or resource) is employed within the creation or presentation of score graphics.
- 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda93a2388190b55a1c821ef6bc64 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8224c688190bb4a362360b03007 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.