Triple
T10414256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NMAT by GMAC |
E245474
|
entity |
| Predicate | allowsRetakes |
P52473
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [NMAT by GMAC, allowsRetakes, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsRetakes Context triple: [NMAT by GMAC, allowsRetakes, yes]
-
A.
hasRetakePolicy
chosen
Indicates that there is a defined policy governing whether and how something (such as an exam, course, or assessment) may be taken again after an initial attempt.
-
B.
infringementRetakeCondition
Indicates the conditions under which a prior infringement triggers or allows a retake (e.g., of a test, exam, or similar activity).
-
C.
attemptLimit
Indicates a restriction on how many times an action or operation may be attempted before it is stopped or blocked.
-
D.
canReinstate
Indicates that one entity has the authority or ability to restore another entity or state to a previous valid or active condition.
-
E.
trialAfter
Indicates that one trial or legal proceeding occurs subsequent to another in time or sequence.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea0ec6fc8190a71af759226a3cba |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:10 p.m.