Triple
T23513730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Direct Unsubsidized Loan |
E572500
|
entity |
| Predicate | interestMayBe |
P152666
|
FINISHED |
| Object | paid while in school |
—
|
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: paid while in school | Statement: [Direct Unsubsidized Loan, interestMayBe, paid while in school]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interestMayBe Context triple: [Direct Unsubsidized Loan, interestMayBe, paid while in school]
-
A.
subjectInterest
Indicates that the subject has an interest in, or is concerned with, the object.
-
B.
interestType
Indicates the specific category or nature of interest that one entity has in relation to another or to a subject.
-
C.
recognizedInterest
Indicates that one entity has formally acknowledged or identified another entity’s interest in something as valid or relevant.
-
D.
publicInterestStatus
Indicates that something has been evaluated or designated in terms of its relevance, importance, or impact to the general public or society at large.
-
E.
collectorInterest
Indicates that one entity has a special interest in acquiring, owning, or seeking out another entity as part of a collection.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 6:08 p.m.