Triple
T134811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SWIFT |
E2724
|
entity |
| Predicate | hasIdentifier |
P1285
|
FINISHED |
| Object | Bank Identifier Code system |
—
|
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: Bank Identifier Code system | Statement: [SWIFT, hasIdentifier, Bank Identifier Code system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIdentifier Context triple: [SWIFT, hasIdentifier, Bank Identifier Code system]
-
A.
hasIdentifierSystem
chosen
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
-
B.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
C.
hasIndex
Indicates that one entity serves as an index or positional reference for another entity within an ordered collection or structure.
-
D.
hasRepresentationIn
Indicates that one entity is represented, depicted, or encoded within another entity, such as a concept, object, or data structure having a corresponding representation in a specific medium or context.
-
E.
hasNationalIdentity
Indicates that an entity possesses or is associated with a particular national identity or nationality.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a3ad908190b6a8652f09ae0cbb |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a25650251c81908a6ea6368cd61198 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.