Triple
T36857298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio Tinto rail network in Pilbara |
E910830
|
entity |
| Predicate | servesMineType |
P44639
|
FINISHED |
| Object | open-pit iron ore mines |
—
|
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: open-pit iron ore mines | Statement: [Rio Tinto rail network in Pilbara, servesMineType, open-pit iron ore mines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesMineType Context triple: [Rio Tinto rail network in Pilbara, servesMineType, open-pit iron ore mines]
-
A.
servesType
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
B.
hasMineType
chosen
Indicates that an entity is associated with or characterized by a specific type or category of mine.
-
C.
mayBeServedBy
Indicates that one entity is a possible or permissible provider or server of another entity, without asserting that the service actually occurs.
-
D.
mayServe
Indicates that one entity is permitted or authorized to provide a service or function to another entity.
-
E.
isServedFor
Indicates that something is provided or presented as suitable or intended for a particular purpose, use, or recipient.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0059f4ffe481908dc500cee9051148 |
completed | May 10, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_6a00593a3c1881909b2ff1a29eb474b3 |
completed | May 10, 2026, 10:08 a.m. |
Created at: May 3, 2026, 4:13 p.m.