Triple
T3395370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Woodbridge Company |
E71514
|
entity |
| Predicate | roleInThomsonReuters |
P38510
|
FINISHED |
| Object | principal shareholder |
—
|
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: principal shareholder | Statement: [The Woodbridge Company, roleInThomsonReuters, principal shareholder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInThomsonReuters Context triple: [The Woodbridge Company, roleInThomsonReuters, principal shareholder]
-
A.
legalProfessionRole
Indicates that one entity holds or performs a specific professional role within the legal domain in relation to another entity or context.
-
B.
legalCaseRole
Indicates the specific role or capacity an entity holds within a legal case, such as plaintiff, defendant, judge, or attorney.
-
C.
legalSystemRole
Indicates the specific function, capacity, or position an entity holds within a legal or judicial system.
-
D.
deJureRole
Indicates that an entity holds a role or position by law or formal right, regardless of whether it is exercised in practice.
-
E.
roleAtInstitution
chosen
Indicates that an entity holds or has held a specific role or position within a particular institution.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb85487088190b8a4ec546ff8a461 |
completed | March 8, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.