Triple
T11292537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koh-i-Noor diamond |
E267362
|
entity |
| Predicate | recutBy |
P98342
|
FINISHED |
| Object | Dutch cutters |
—
|
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: Dutch cutters | Statement: [Koh-i-Noor diamond, recutBy, Dutch cutters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recutBy Context triple: [Koh-i-Noor diamond, recutBy, Dutch cutters]
-
A.
recastBy
Indicates that an existing role, character, or part has been newly assigned to a different performer or entity than before.
-
B.
recastOf
Indicates that one entity is a new or different version, adaptation, or reinterpretation of another, typically replacing or redoing the original in a similar role or context.
-
C.
recombinedBy
Indicates that something (such as genetic material, data, or components) has been formed or altered through a recombination process carried out by a specified agent or mechanism.
-
D.
recurs
Indicates that an event, condition, or pattern happens again, often repeatedly or at regular intervals, after having occurred before.
-
E.
recreated
Indicates that an entity has been created again or restored, typically after being removed, destroyed, or significantly altered.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e989fdac81909a4a75f1f68b55c6 |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a6ca2c8190afdc24b61ccd3f8a |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.