Triple
T15923685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Happy Diamonds |
E386152
|
entity |
| Predicate | gemSettingType |
P120563
|
FINISHED |
| Object | free-moving setting |
—
|
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: free-moving setting | Statement: [Happy Diamonds, gemSettingType, free-moving setting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gemSettingType Context triple: [Happy Diamonds, gemSettingType, free-moving setting]
-
A.
gemType
Indicates the specific kind or category of gemstone associated with an entity.
-
B.
gemUse
Indicates that an entity makes use of, applies, or benefits from a particular gem.
-
C.
geometricSetting
Indicates the spatial or geometric context within which an object, relation, or event is defined or occurs.
-
D.
usedAsSettingFor
Indicates that one entity serves as the backdrop, location, or environment in which another entity (such as an event, story, or activity) takes place.
-
E.
coversSetting
Indicates that one entity includes or addresses a particular setting or context within its scope.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e172b213e481909ee0c05e16229a26 |
completed | April 16, 2026, 11:37 p.m. |
Created at: April 10, 2026, 4:52 a.m.