Triple
T29434885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bank |
E746541
|
entity |
| Predicate | hasOwnerTrait |
P167169
|
FINISHED |
| Object | ruthless hotel magnate Willy Bank |
—
|
NE NERFINISHED |
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: ruthless hotel magnate Willy Bank | Statement: [The Bank, hasOwnerTrait, ruthless hotel magnate Willy Bank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOwnerTrait Context triple: [The Bank, hasOwnerTrait, ruthless hotel magnate Willy Bank]
-
A.
hasOwnerShare
Indicates that an entity holds a specified ownership stake or share in another entity or asset.
-
B.
hasOwnerAction
Indicates that an owner performs, initiates, or is responsible for a specific action related to the owned entity.
-
C.
hasCapitalOwnerRole
Indicates that an entity holds the role or status of owning capital in relation to another entity or asset.
-
D.
hasOwnerStructure
Indicates that an entity is associated with, or governed by, a particular ownership structure or ownership arrangement.
-
E.
hasCoOwner
Indicates that an entity shares ownership of something with one or more other entities.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66acbd408819094a2a0d855ab58a1 |
completed | May 2, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 28, 2026, 3:15 p.m.