Triple
T11257493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transnet Freight Rail |
E266474
|
entity |
| Predicate | primaryCustomerSector |
P70059
|
FINISHED |
| Object | mining industry |
—
|
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: mining industry | Statement: [Transnet Freight Rail, primaryCustomerSector, mining industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCustomerSector Context triple: [Transnet Freight Rail, primaryCustomerSector, mining industry]
-
A.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
B.
primaryBusinessArea
chosen
Indicates the main field, sector, or domain in which an entity primarily conducts its business activities.
-
C.
economicSectorDominant
Indicates that one economic sector holds a leading or controlling position relative to others in terms of influence, output, or importance.
-
D.
sectoralCoverage
Indicates the specific sectors, industries, or domains to which something (such as a policy, agreement, or dataset) applies or extends.
-
E.
majorCustomer
Indicates that one entity is a primary or high-value customer of another entity, typically contributing a significant portion of business or revenue.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e935b85c819085e1abf2dd4099c5 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d78793c00481908a3f764b610b77a4 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.