Triple
T38492209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wernher, Beit & Co. |
E918082
|
entity |
| Predicate | capitalSourceFor |
P65105
|
FINISHED |
| Object | South African mining companies |
—
|
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: South African mining companies | Statement: [Wernher, Beit & Co., capitalSourceFor, South African mining companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalSourceFor Context triple: [Wernher, Beit & Co., capitalSourceFor, South African mining companies]
-
A.
sourceOfCapital
chosen
Indicates the origin or provider from which an entity obtains its financial capital or funding.
-
B.
capitalSince
Indicates that an entity has served as the capital of another entity starting from a specified point in time.
-
C.
fundingSourceProposed
Indicates that a particular source of funding has been suggested or put forward to finance an activity, project, or entity.
-
D.
fundFinancedBy
Indicates that a particular fund receives its financial resources or backing from a specified source or entity.
-
E.
capitalToday
Indicates that a location is serving as the capital city of a political or administrative entity at the present time.
- 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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: May 3, 2026, 4:31 p.m.