Triple
T4949034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Control Video Corporation |
E111122
|
entity |
| Predicate | roleOfWilliamVonMeister |
P60121
|
FINISHED |
| Object | founder |
—
|
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: founder | Statement: [Control Video Corporation, roleOfWilliamVonMeister, founder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfWilliamVonMeister Context triple: [Control Video Corporation, roleOfWilliamVonMeister, founder]
-
A.
roleOfVictorFeldbrill
Indicates the professional role, position, or capacity held by Victor Feldbrill in a given context.
-
B.
roleOfChrisBauermeister
Indicates that the specified role or position is held or performed by Chris Bauermeister.
-
C.
roleInOperationReinhard
Indicates that an entity held a specific role or participated in some capacity in Operation Reinhard, the Nazi plan to exterminate Jews in occupied Poland during the Holocaust.
-
D.
designedRole
Indicates that one entity has been created, configured, or intended to serve a particular function, purpose, or role in relation to another entity.
-
E.
roleOfPeter Seligmann
Indicates that the specified role or position is held by Peter Seligmann.
- 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7166bb6c8190a40775ac8bb723a8 |
completed | March 20, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6fa2d2088190ae444d3d0e47d5d2 |
completed | March 20, 2026, 4:02 p.m. |
Created at: March 20, 2026, 1:31 p.m.