Triple
T17613575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBA |
E429023
|
entity |
| Predicate | isWidelyHeldBy |
P121485
|
FINISHED |
| Object | Institutional investors |
—
|
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: Institutional investors | Statement: [CBA, isWidelyHeldBy, Institutional investors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWidelyHeldBy Context triple: [CBA, isWidelyHeldBy, Institutional investors]
-
A.
isWidelyHeld
chosen
Indicates that a belief, opinion, or view is shared by a large number of people or is broadly accepted within a group or population.
-
B.
isWidelyTraded
Indicates that an asset or item is frequently bought and sold across many participants or markets, resulting in high trading activity and liquidity.
-
C.
isWidelyUsed
Indicates that something is commonly or extensively utilized across many contexts, users, or situations.
-
D.
isWidelyKnown
Indicates that something is generally recognized or familiar to a large number of people.
-
E.
typicalNumberOfHolders
Indicates the usual or expected number of entities that hold or possess a given item, role, or resource.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d2fd96481908c9f3b566fca6907 |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.