Triple
T31315732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Message in a Bottle (Taylor’s Version) (From the Vault) |
E798589
|
entity |
| Predicate | hasVaultDesignation |
P974
|
FINISHED |
| Object | From the Vault |
—
|
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: From the Vault | Statement: [Message in a Bottle (Taylor’s Version) (From the Vault), hasVaultDesignation, From the Vault]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVaultDesignation Context triple: [Message in a Bottle (Taylor’s Version) (From the Vault), hasVaultDesignation, From the Vault]
-
A.
hasVaultStatus
Indicates that an entity possesses a particular vault-related state or condition, such as being stored in, protected by, or associated with a vault.
-
B.
hasKVDesignation
Indicates that an entity has been assigned a specific KV (classification or designation) label or code.
-
C.
hasVaultType
Indicates that an entity is associated with or classified by a particular type or category of vault.
-
D.
hasGoldVault
Indicates that one entity possesses or contains a vault specifically used for storing gold.
-
E.
hasDesignation
chosen
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:15 p.m.