Triple
T26775673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multistate Bar Examination |
E670112
|
entity |
| Predicate | isHighStakesExam |
P78860
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Multistate Bar Examination, isHighStakesExam, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHighStakesExam Context triple: [Multistate Bar Examination, isHighStakesExam, true]
-
A.
isHighStakes
chosen
Indicates that the situation, event, or decision involves significant risk, consequences, or potential impact, making the outcome particularly critical.
-
B.
examType
Indicates the specific category or format of an exam associated with an assessment or testing event.
-
C.
isMidterm
Indicates that an event, exam, or assessment occurs in the middle portion of an academic term or course.
-
D.
exam
Indicates that an entity administers, takes, or is associated with a formal test or assessment of knowledge, skills, or performance.
-
E.
entranceExam
Indicates that an entity is required to pass or participate in an entrance examination as a condition for admission or access to another entity.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6193294948190adeecbad17283103 |
completed | May 2, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 4:04 a.m.