Triple
T26220281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cullinan mine |
E655746
|
entity |
| Predicate | acquiredByPetraDiamondsYear |
P15703
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Cullinan mine, acquiredByPetraDiamondsYear, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquiredByPetraDiamondsYear Context triple: [Cullinan mine, acquiredByPetraDiamondsYear, 2008]
-
A.
laterAcquiredBy
Indicates that one entity was acquired by another entity at a later point in time, after some prior state or ownership.
-
B.
wasAcquiredIn
Indicates that one entity obtained ownership or control of another entity through an acquisition event that occurred at a specific time or in a specific transaction.
-
C.
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).
-
D.
acquisitionCompletedYear
chosen
Indicates the calendar year in which an acquisition transaction was fully completed.
-
E.
couldBeAcquiredBy
Indicates that one entity is a potential target to be obtained, bought, or taken over by another entity.
- 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_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 26, 2026, 8:55 p.m.