Triple
T9431018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquamarine |
E227373
|
entity |
| Predicate | typicalCut |
P84047
|
FINISHED |
| Object | emerald 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: emerald cut | Statement: [Aquamarine, typicalCut, emerald cut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCut Context triple: [Aquamarine, typicalCut, emerald cut]
-
A.
hasTypicalCut
chosen
Indicates that one entity is characterized by or associated with a standard or typical type of cut of another entity.
-
B.
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.
-
C.
isCutInto
Indicates that one entity is divided or separated into pieces or segments that become the other entity.
-
D.
cuttingStyle
Indicates the manner or technique in which something is cut or shaped.
-
E.
typicalSegmentType
Indicates that something is classified as belonging to a usual or characteristic type of segment within a broader structure or sequence.
- 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_69ca8437a7ac81908651de48f2d2141d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e5ed7408190beda5fb078e9345a |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.