Triple
T11864720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guarantee Credit |
E282251
|
entity |
| Predicate | linkedComponent |
P101946
|
FINISHED |
| Object | Savings Credit |
—
|
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: Savings Credit | Statement: [Guarantee Credit, linkedComponent, Savings Credit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedComponent Context triple: [Guarantee Credit, linkedComponent, Savings Credit]
-
A.
linkedPosition
Indicates that one position is associated or connected to another position in a defined way.
-
B.
linkedByStructure
Indicates that two entities are connected or associated through a shared structural element, configuration, or framework.
-
C.
linkedFigure
Indicates that one figure is associated or connected to another figure, typically as a reference or related visual element.
-
D.
linkedLocation
Indicates that one location is associated or connected to another location in a meaningful way, such as being related, referenced, or contextually tied.
-
E.
linkType
Indicates the specific kind or category of relationship that connects two linked entities.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a73883508190a78b5f4ba4a220df |
completed | April 10, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69d8a2589f0c8190ad82ff11acabae93 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.