Triple
T23558712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franklin Swift |
E579162
|
entity |
| Predicate | relationshipTypeWithZoraBanks |
P152791
|
FINISHED |
| Object | romantic partner |
—
|
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: romantic partner | Statement: [Franklin Swift, relationshipTypeWithZoraBanks, romantic partner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipTypeWithZoraBanks Context triple: [Franklin Swift, relationshipTypeWithZoraBanks, romantic partner]
-
A.
financialRelationshipWith
Indicates a financial connection or association between entities, such as ownership, investment, funding, or other monetary ties.
-
B.
connectsBank
Indicates a relationship where one entity serves to link or provide access between another entity and a bank or banking service.
-
C.
tributaryBank
Indicates that one bank or financial institution is a subsidiary or dependent branch of another, larger or primary bank.
-
D.
relationshipToStandingOrders
Indicates the nature or status of an entity’s connection or applicability to existing standing orders.
-
E.
trackBanking
Indicates monitoring, recording, or managing banking-related activities or transactions associated with an entity.
- 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af6663e0819081d654da38cf3aa9 |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:12 p.m.