Triple
T16229568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novagems |
E393942
|
entity |
| Predicate | designedToMimic |
P31513
|
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: [Novagems, designedToMimic, precious stones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToMimic Context triple: [Novagems, designedToMimic, precious stones]
-
A.
emulates
chosen
Indicates that one entity imitates or reproduces the behavior, function, or characteristics of another.
-
B.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
C.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
D.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
E.
designedToFace
Indicates that one entity has been intentionally oriented or configured so that its front, surface, or primary direction points toward another entity or reference direction.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d2889688190ac04e4e9479cabf4 |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.