Triple
T7295553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cullinan II |
E164511
|
entity |
| Predicate | cuttingStyle |
P75445
|
FINISHED |
| Object | cushion cut |
—
|
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 | Statement: [Cullinan II, cuttingStyle, cushion cut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cuttingStyle Context triple: [Cullinan II, cuttingStyle, cushion cut]
-
A.
isCutInto
Indicates that one entity is divided or separated into pieces or segments that become the other entity.
-
B.
bladeType
Indicates the specific kind or category of blade associated with an object or entity.
-
C.
commonCut
Indicates that two or more entities share at least one identical segment or portion that has been cut or divided in the same way.
-
D.
passingStyle
Indicates the manner or technique by which something (typically a ball or object) is passed from one entity to another.
-
E.
hasCut
Indicates that one entity has made or possesses a cut in, on, or through another entity.
- F. None of above. chosen
Provenance (4 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb8d0c6c8190b32cd08b9a5d96cc |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76c5fbc8190b378830082f11cb0 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6e82b0f9881909d29c99af1ea0dbf |
completed | March 27, 2026, 8:27 p.m. |
Created at: March 27, 2026, 3 p.m.