Triple
T22944085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petal |
E569817
|
entity |
| Predicate | underwritingApproach |
P10363
|
FINISHED |
| Object | goes beyond traditional credit scores |
—
|
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: goes beyond traditional credit scores | Statement: [Petal, underwritingApproach, goes beyond traditional credit scores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underwritingApproach Context triple: [Petal, underwritingApproach, goes beyond traditional credit scores]
-
A.
complianceApproach
Indicates the method or strategy an entity uses to meet, adhere to, or enforce specified rules, standards, or regulatory requirements.
-
B.
usedToApproach
Indicates that one entity employed another entity as a means or method to move closer to or reach a target entity or location.
-
C.
includesApproach
chosen
Indicates that one entity incorporates, utilizes, or is characterized by a particular method, strategy, or approach in relation to another entity or context.
-
D.
standardApproach
Indicates that an entity uses or follows a commonly accepted, conventional, or typical method for addressing a task or problem.
-
E.
standardizationApproach
Indicates the method or strategy used to establish, implement, or align with a common standard across entities or processes.
- 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_69e2459199d08190a8184ee2aa935842 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1819b65dc8190b9456346e7284ddf |
completed | April 29, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:45 p.m.