Triple
T26263437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cullinan diamond |
E656914
|
entity |
| Predicate | discoveredInPlace |
P3986
|
FINISHED |
| Object | Premier Mine |
—
|
NE NERFINISHED |
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: Premier Mine | Statement: [Cullinan diamond, discoveredInPlace, Premier Mine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredInPlace Context triple: [Cullinan diamond, discoveredInPlace, Premier Mine]
-
A.
wasDiscoveredIn
chosen
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
-
B.
discoveredInCountry
Indicates that something was discovered within the geographical boundaries or jurisdiction of a specified country.
-
C.
discoveredInCity
Indicates that something was found, identified, or uncovered within the boundaries of a particular city.
-
D.
discoveredAsPartOf
Indicates that something was found, identified, or revealed in the course of a larger activity, process, or investigation of which it formed a component.
-
E.
inhabitedIn
Indicates that an entity lives, resides, or has its dwelling within a specified place or location.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 26, 2026, 9:10 p.m.