Triple
T26263474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cullinan II |
E656914
|
entity |
| Predicate | cutShape |
P26148
|
FINISHED |
| Object | cushion-cut brilliant |
—
|
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: cushion-cut brilliant | Statement: [Cullinan II, cutShape, cushion-cut brilliant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cutShape Context triple: [Cullinan II, cutShape, cushion-cut brilliant]
-
A.
cutRule
Indicates that one entity applies or enforces a rule that removes, prunes, or eliminates certain elements or possibilities from consideration.
-
B.
cutFormat
chosen
Indicates that one entity trims or shapes another entity into a specified format or pattern.
-
C.
cutBy
Indicates that one entity is divided, severed, or shaped as a result of another entity performing a cutting action on it.
-
D.
coreShape
Indicates that one entity serves as the primary or central shape or geometric form of another entity.
-
E.
cuttingStyle
Indicates the manner or technique in which something is cut or shaped.
- 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_69f60e022a5881908a4582d8d9cbbb38 |
completed | May 2, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 9:10 p.m.