Triple
T26809883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamonds and Sapphires |
E671957
|
entity |
| Predicate | hasNameInspiration |
P132742
|
FINISHED |
| Object | precious stones |
—
|
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: precious stones | Statement: [Diamonds and Sapphires, hasNameInspiration, precious stones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInspiration Context triple: [Diamonds and Sapphires, hasNameInspiration, precious stones]
-
A.
nameGivesRiseTo
Indicates that one name, term, or designation leads to, causes, or results in the emergence or establishment of another.
-
B.
usedAsNamesakeFor
chosen
Indicates that one entity serves as the source or inspiration for the name given to another entity.
-
C.
shapeInspiredNickname
Indicates that one entity’s physical shape or form served as the inspiration for another entity’s nickname.
-
D.
influencedNameOf
Indicates that one entity has affected or shaped the naming or choice of name of another entity.
-
E.
nameEvokes
Indicates that one entity’s name elicits, suggests, or brings to mind an association, image, or feeling related to another entity.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 27, 2026, 4:28 a.m.