Triple
T23123064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PLUS Loan |
E576951
|
entity |
| Predicate | cannotBeTransferredToStudent |
P18801
|
FINISHED |
| Object | Parent PLUS Loan |
—
|
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: Parent PLUS Loan | Statement: [PLUS Loan, cannotBeTransferredToStudent, Parent PLUS Loan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotBeTransferredToStudent Context triple: [PLUS Loan, cannotBeTransferredToStudent, Parent PLUS Loan]
-
A.
nonTransferable
chosen
Indicates that a right, asset, or privilege cannot be legally or contractually transferred from one party to another.
-
B.
cannotBeAwardedTo
Indicates that a particular entity is ineligible to receive a specified award, prize, or recognition.
-
C.
cannotBelongTo
Indicates that one entity is not allowed or not able to be a member, part, or element of another entity or group.
-
D.
cannotIntroduce
Indicates that one entity is not permitted or able to introduce another entity (such as a person, concept, or item) into a given context or to a third party.
-
E.
cannotChange
Indicates that an entity is unable or not permitted to alter the state, value, or properties of another entity or relationship.
- 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_69e245f6c2e881909a228fdcfeb7c7d3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e517a0481909829a73fdf255d1c |
completed | April 29, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:59 p.m.