Triple
T4362750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girobank |
E98697
|
entity |
| Predicate | usedChannel |
P4793
|
FINISHED |
| Object | mail-based payment instructions |
—
|
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: mail-based payment instructions | Statement: [Girobank, usedChannel, mail-based payment instructions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedChannel Context triple: [Girobank, usedChannel, mail-based payment instructions]
-
A.
originalChannel
Indicates the communication channel or medium through which something was first created, sent, or published.
-
B.
usesSeparateChannelFor
Indicates that one entity communicates with or accesses another entity through a distinct, dedicated channel separate from other communications or interactions.
-
C.
usesChannelBandwidth
Indicates that one entity consumes or occupies a portion of the available bandwidth on a communication channel.
-
D.
virtualChannel
Indicates that one entity is linked to another through a non-physical, software-defined communication channel used for transmitting data or signals.
-
E.
usedMedium
chosen
Indicates that an action or communication was carried out through a particular medium or channel.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351e5ee308190a9271e73689b4a2b |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:16 p.m.