Triple
T1955284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regent Diamond |
E42253
|
entity |
| Predicate | caratWeight |
P33510
|
FINISHED |
| Object | 140.64 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: 140.64 carats | Statement: [Regent Diamond, caratWeight, 140.64 carats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caratWeight Context triple: [Regent Diamond, caratWeight, 140.64 carats]
-
A.
hasProng
Indicates that one entity possesses, includes, or is equipped with a prong or prongs as part of its structure or design.
-
B.
hasNumberOfProngs
Indicates the relationship specifying how many prongs an object or entity possesses.
-
C.
stateGemstone
Indicates a relationship where a state is officially associated with or designated a particular gemstone.
-
D.
hasRingComposition
Indicates that one entity is composed of, or structurally organized around, a ring-like arrangement or circular structure.
-
E.
hasBirthstone
Indicates that a person or entity is associated with a particular gemstone traditionally recognized as their birthstone.
- 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_69a8870eea088190a38781990812a9bc |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb353aa8c81909810347f9981a02f |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff3eda88190b643994cb4dfb8df |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb1ddccbc8190bf2bd8bac673c0c5 |
completed | March 7, 2026, 5:04 a.m. |
Created at: March 4, 2026, 7:36 p.m.