Triple
T28636801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dresden Green Diamond |
E724810
|
entity |
| Predicate | approximateCaratWeight |
P33510
|
FINISHED |
| Object | 41 carats |
—
|
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: 41 carats | Statement: [Dresden Green Diamond, approximateCaratWeight, 41 carats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateCaratWeight Context triple: [Dresden Green Diamond, approximateCaratWeight, 41 carats]
-
A.
caratWeight
chosen
Indicates the weight of a gemstone or diamond, measured in carats, associated with an item or entity.
-
B.
approximateWeightInPounds
Indicates the estimated weight of an entity expressed in pounds, rather than an exact measured value.
-
C.
approximateMass
Indicates that one entity has a mass value that is an estimate or close approximation of the mass of another entity.
-
D.
intendedWeight
Indicates the target or desired weight that an entity is meant or planned to have, rather than its current actual weight.
-
E.
approximateDiameter
Indicates that one entity specifies the estimated or rough measurement of another entity’s diameter.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 28, 2026, 4:41 a.m.