Triple
T6970372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Electronic Funds Transfer system |
E161583
|
entity |
| Predicate | accessChannel |
P71475
|
FINISHED |
| Object | bank branch |
—
|
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 branch | Statement: [National Electronic Funds Transfer system, accessChannel, bank branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessChannel Context triple: [National Electronic Funds Transfer system, accessChannel, bank branch]
-
A.
availabilityChannel
chosen
Indicates the medium or channel through which something (such as a product, service, or resource) is made available or can be accessed.
-
B.
communicationChannel
Indicates a medium or method through which information is transmitted between parties.
-
C.
hasCustomerServiceChannel
Indicates that an entity provides or is associated with a specific channel or medium through which customer service interactions can occur.
-
D.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
E.
communicationCapability
Indicates that one entity has the ability or means to communicate with another entity through some channel or modality.
- 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_69c68854a0d88190bc0bf82263f1afce |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db1649288190a52c7dab57b3c7dc |
completed | March 27, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c262508190a7708b3d9cf23d7c |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:30 p.m.