Triple
T20431744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BNS |
E501147
|
entity |
| Predicate | hasOwnershipRights |
P39434
|
FINISHED |
| Object | voting rights in The Bank of Nova Scotia |
—
|
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: voting rights in The Bank of Nova Scotia | Statement: [BNS, hasOwnershipRights, voting rights in The Bank of Nova Scotia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOwnershipRights Context triple: [BNS, hasOwnershipRights, voting rights in The Bank of Nova Scotia]
-
A.
hasRightsOver
chosen
Indicates that one entity possesses legal, moral, or formal entitlements or authority over another entity.
-
B.
hasRightsStatus
Indicates that an entity is associated with a particular legal or usage rights condition or status.
-
C.
legallyOwns
Indicates that one entity holds lawful ownership rights over another entity or asset.
-
D.
hasOwnerShare
Indicates that an entity holds a specified ownership stake or share in another entity or asset.
-
E.
hasOwnershipForm
Indicates that an entity possesses a particular legal or organizational form of ownership (such as private, public, or cooperative).
- 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_69e0b4ab3cfc8190ac9bf32e932316b1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685eaa4c8819083d1d7aee0f998a6 |
completed | April 20, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:31 a.m.