Triple
T14017442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australia–China relations |
E337238
|
entity |
| Predicate | australiaMajorExportToChina |
P3026
|
FINISHED |
| Object | iron ore |
—
|
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: iron ore | Statement: [Australia–China relations, australiaMajorExportToChina, iron ore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: australiaMajorExportToChina Context triple: [Australia–China relations, australiaMajorExportToChina, iron ore]
-
A.
AustraliaOvers
Indicates a relationship where one entity surpasses, exceeds, or goes beyond another in the specific context associated with Australia.
-
B.
majorExport
chosen
Indicates that something is a primary or significant export product or resource of a given entity (such as a country or region).
-
C.
numberOfVictimsFromAustralia
Indicates the count of victims whose origin or nationality is Australia.
-
D.
isMajorProducerOf
Indicates that an entity plays a leading or highly significant role in producing or supplying a particular product, resource, or output.
-
E.
arrivalInAustralia
Indicates that an entity has arrived in Australia, marking the completion of its journey to that country.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f3b5b088190a58715779d2c46a6 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.