Triple
T21479493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Weipa Mine |
E529950
|
entity |
| Predicate | materialTransport |
P91189
|
FINISHED |
| Object | conveyor systems |
—
|
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: conveyor systems | Statement: [East Weipa Mine, materialTransport, conveyor systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialTransport Context triple: [East Weipa Mine, materialTransport, conveyor systems]
-
A.
materialTransportedTo
Indicates that a material is moved or conveyed from one location or entity to another specified destination.
-
B.
materialTransportedFrom
Indicates that a material or substance is moved or carried from a specified source location to another place.
-
C.
mainCargo
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
-
D.
transportedWith
Indicates that one entity was moved or carried together with another entity as part of the same transport event.
-
E.
commonlyTransportedIn
chosen
Indicates that something is usually carried, moved, or conveyed using a particular vehicle, container, or mode of transport.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea1a37a88190845810cbcacbad65 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:20 p.m.