Triple
T26263453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cullinan diamond |
E656914
|
entity |
| Predicate | cuttingCompletedInYear |
P75450
|
FINISHED |
| Object | 1908 |
—
|
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: 1908 | Statement: [Cullinan diamond, cuttingCompletedInYear, 1908]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cuttingCompletedInYear Context triple: [Cullinan diamond, cuttingCompletedInYear, 1908]
-
A.
cuttingCompletionDate
chosen
Indicates the date on which a cutting process or operation is completed.
-
B.
cutOffDateYear
Indicates the calendar year that serves as the cutoff point beyond which something no longer applies, is valid, or is considered.
-
C.
workCompletionYear
Indicates the calendar year in which a particular work, project, or task was completed.
-
D.
revisionCompletionYear
Indicates the year in which a revision of something (e.g., a work, document, or item) was completed.
-
E.
completedAsThroughRouteYear
Indicates that an entity was completed in a specific year specifically in its form or function as a through route.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60e022a5881908a4582d8d9cbbb38 |
completed | May 2, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:10 p.m.