Triple
T30875404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kimberley kimberlite fields |
E786462
|
entity |
| Predicate | approximateNumberOfPipes |
P196123
|
FINISHED |
| Object | dozens of kimberlite bodies |
—
|
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: dozens of kimberlite bodies | Statement: [Kimberley kimberlite fields, approximateNumberOfPipes, dozens of kimberlite bodies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateNumberOfPipes Context triple: [Kimberley kimberlite fields, approximateNumberOfPipes, dozens of kimberlite bodies]
-
A.
hasPipes
Indicates that one entity is equipped with, contains, or is connected to one or more pipes.
-
B.
numberOfOrganPipes
Indicates the quantitative relationship specifying how many organ pipes are associated with a given organ or organ-related entity.
-
C.
numberOfTubes
Indicates the quantity of tubes associated with or contained by a given entity.
-
D.
numberOfPumps
Indicates the quantity of pumps associated with or required by an entity or system.
-
E.
numberOfTrunksApprox
Indicates an approximate count of trunks associated with an entity, rather than an exact number.
- F. None of above. chosen
Provenance (4 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_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
| PDg | Predicate description generation | batch_69fe08d1b3f881908eccb74cb0d246dc |
completed | May 8, 2026, 4:01 p.m. |
Created at: April 29, 2026, 8:48 p.m.