Triple

T23123038
Position Surface form Disambiguated ID Type / Status
Subject PLUS Loan E576951 entity
Predicate creditHistoryRequirement P111831 FINISHED
Object no adverse credit history 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 adverse credit history | Statement: [PLUS Loan, creditHistoryRequirement, no adverse credit history]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: creditHistoryRequirement
Context triple: [PLUS Loan, creditHistoryRequirement, no adverse credit history]
  • A. typicalCreditRequirement
    Indicates the usual or standard amount of credit that is generally required or expected in a given context.
  • B. creditRequired
    Indicates that a certain amount or type of credit must be obtained or possessed as a prerequisite for something (such as access, participation, or completion).
  • C. borrowerRequirement chosen
    Indicates that certain conditions or qualifications must be met by a borrower in order to be eligible for a loan or credit arrangement.
  • D. hasCreditRating
    Indicates that an entity is assigned a formal assessment of its creditworthiness, typically expressed as a credit score or rating.
  • E. creditCheckRequired
    Indicates that a verification of an entity’s creditworthiness must be performed before proceeding with a related action or transaction.
  • 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.