Triple
T27660741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radius Bank |
E697113
|
entity |
| Predicate | acquisitionCompletedDate |
P2754
|
FINISHED |
| Object | February 2021 |
—
|
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: February 2021 | Statement: [Radius Bank, acquisitionCompletedDate, February 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionCompletedDate Context triple: [Radius Bank, acquisitionCompletedDate, February 2021]
-
A.
acquisitionDate
chosen
Indicates the date on which one entity formally acquires or takes ownership of another entity.
-
B.
acquisitionCompletedYear
Indicates the calendar year in which an acquisition transaction was fully completed.
-
C.
wasAcquiredIn
Indicates that one entity obtained ownership or control of another entity through an acquisition event that occurred at a specific time or in a specific transaction.
-
D.
accessionDate
Indicates the date on which an item, record, or entity was formally added to a collection, system, or repository.
-
E.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 2:36 p.m.