Triple
T11292489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koh-i-Noor diamond |
E267362
|
entity |
| Predicate | weightBeforeRecut |
P9777
|
FINISHED |
| Object | 186 carats (approximate) |
—
|
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: 186 carats (approximate) | Statement: [Koh-i-Noor diamond, weightBeforeRecut, 186 carats (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weightBeforeRecut Context triple: [Koh-i-Noor diamond, weightBeforeRecut, 186 carats (approximate)]
-
A.
wasPreviouslyMeasuredAs
chosen
Indicates that an entity had a specific measurement or value at an earlier time, which may differ from its current measurement.
-
B.
weight
Indicates a relationship where a numerical value quantifies how heavy an entity is, often used to measure or compare mass or load.
-
C.
وزن
Indicates a relationship where one entity has, measures, or is characterized by a certain weight or mass.
-
D.
cutDown
Indicates that an agent causes something standing or elevated (such as a tree or structure) to fall or be reduced by cutting.
-
E.
cutBy
Indicates that one entity is divided, severed, or shaped as a result of another entity performing a cutting action on it.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e989fdac81909a4a75f1f68b55c6 |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a6ca2c8190afdc24b61ccd3f8a |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.