Triple
T5587765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Svalbard Global Seed Vault |
E146796
|
entity |
| Predicate | firstSeedDepositDate |
P64922
|
FINISHED |
| Object | 2008-02-26 |
—
|
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: 2008-02-26 | Statement: [Svalbard Global Seed Vault, firstSeedDepositDate, 2008-02-26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSeedDepositDate Context triple: [Svalbard Global Seed Vault, firstSeedDepositDate, 2008-02-26]
-
A.
firstHolderDate
Indicates the date on which an entity first became the holder or owner of another entity (e.g., an asset, title, or right).
-
B.
firstBlockMinedDate
Indicates the date on which the first block associated with the entity was mined.
-
C.
firstMintingPeriodStart
Indicates the point in time when the initial minting period for a given asset or token begins.
-
D.
firstDeployedAt
Indicates the date and time when an entity was initially put into use or made operational.
-
E.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
- 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_69c009036c408190981a8d690b679b67 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0209e892c8190b936a05ef2a14d36 |
completed | March 22, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f4032408190a4f0d2eb21ebd870 |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:38 p.m.