Triple
T30875399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kimberley kimberlite fields |
E786462
|
entity |
| Predicate | transportedToSurface |
P74851
|
FINISHED |
| Object | xenocrystic diamonds |
—
|
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: xenocrystic diamonds | Statement: [Kimberley kimberlite fields, transportedToSurface, xenocrystic diamonds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportedToSurface Context triple: [Kimberley kimberlite fields, transportedToSurface, xenocrystic diamonds]
-
A.
transportedAfter
Indicates that one entity is transported only after the transportation of another entity has occurred in time.
-
B.
transportedToEarthBy
Indicates that an entity was moved or carried from another location or context to Earth by a specified agent or means.
-
C.
wasTransportedTo
chosen
Indicates that an entity was moved or carried from one location to another, resulting in its arrival at the specified destination.
-
D.
transportedOver
Indicates that something is moved or carried across or along a specified medium, route, or surface.
-
E.
transportedFor
Indicates that one entity was moved or carried from one place to another for the benefit, use, or purpose of another entity or activity.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: April 29, 2026, 8:48 p.m.