Triple
T23513735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Direct Unsubsidized Loan |
E572500
|
entity |
| Predicate | coSignerRequired |
P63096
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Direct Unsubsidized Loan, coSignerRequired, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coSignerRequired Context triple: [Direct Unsubsidized Loan, coSignerRequired, no]
-
A.
noticeSignatoriesRequirement
Indicates that a notice must be provided to, or acknowledged by, the required signatories.
-
B.
coSignedWith
Indicates that an entity has jointly signed a document, agreement, or obligation together with another entity.
-
C.
co-signer
Indicates that one entity agrees to share legal and financial responsibility for another entity’s obligation, such as a loan or contract.
-
D.
requiresSignatureOf
chosen
Indicates that one entity must obtain or depend on the formal signature or signed approval of another entity.
-
E.
initialSignatoriesIncluded
Indicates that the specified entities were part of the original group that formally signed or endorsed an agreement or document.
- 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_69e245b5e4208190bac8a6509867e394 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa80174c819088c9c19fdcf2a133 |
completed | April 29, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:08 p.m.