Triple
T12068838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logical Reasoning (LSAT) |
E287367
|
entity |
| Predicate | scoreContribution |
P10576
|
FINISHED |
| Object | significant portion of LSAT score |
—
|
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: significant portion of LSAT score | Statement: [Logical Reasoning (LSAT), scoreContribution, significant portion of LSAT score]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoreContribution Context triple: [Logical Reasoning (LSAT), scoreContribution, significant portion of LSAT score]
-
A.
scoreAssignment
Indicates evaluating and assigning a grade or numerical score to an assignment.
-
B.
scoreScale
Indicates the scale or range on which a score or rating is expressed or measured.
-
C.
scoring
chosen
Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
-
D.
scoreUsedFor
Indicates that a particular score or rating is used for a specific purpose, decision, or downstream process.
-
E.
scoreEffect
Indicates the impact or change that an action, event, or condition has on a score or scoring outcome.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bda47c8190b94860b31df4a98c |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:48 p.m.