Triple
T3325373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commonwealth Bank of Australia (central banking functions) |
E69902
|
entity |
| Predicate | performedFunction |
P47301
|
FINISHED |
| Object | central banking |
—
|
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: central banking | Statement: [Commonwealth Bank of Australia (central banking functions), performedFunction, central banking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedFunction Context triple: [Commonwealth Bank of Australia (central banking functions), performedFunction, central banking]
-
A.
performed
Indicates that an entity carried out, executed, or conducted a specific action, task, or activity.
-
B.
performedTo
Indicates that an action or performance is directed toward or carried out on a particular entity.
-
C.
performedWith
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
D.
performedFirst
Indicates that one entity carried out an action or event before another entity did.
-
E.
performedEvent
Indicates that an entity carried out, executed, or was responsible for a particular event.
- 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_69ad85a1829881908942c14075644d0d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb16ca13c8190aea8caed8ccd9b88 |
completed | March 8, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada52716ec81908e89688a81039394 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:11 p.m.