Triple
T26220306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cullinan mine |
E655746
|
entity |
| Predicate | largestRoughDiamondFoundCarat |
P33510
|
FINISHED |
| Object | 3106 |
—
|
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: 3106 | Statement: [Cullinan mine, largestRoughDiamondFoundCarat, 3106]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: largestRoughDiamondFoundCarat Context triple: [Cullinan mine, largestRoughDiamondFoundCarat, 3106]
-
A.
famousDiamondProduced
Indicates that a particular diamond is widely recognized as famous and was produced or originated from a specific source (such as a mine, region, or producer).
-
B.
caratWeight
chosen
Indicates the weight of a gemstone or diamond, measured in carats, associated with an item or entity.
-
C.
isLargestMeteoriteIn
Indicates that a meteorite is the largest (by a specified measure, typically size or mass) among all meteorites found within a given location or region.
-
D.
hasDiamondCount
Indicates that an entity possesses or is associated with a specified number of diamonds.
-
E.
largestFigureLengthApprox
Indicates an approximate measurement of the length of the largest figure involved in the relationship or context.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 8:55 p.m.