Triple
T14516098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suburban Legends (Taylor’s Version) (From The Vault) |
E340522
|
entity |
| Predicate | hasVaultStatus |
P114553
|
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: [Suburban Legends (Taylor’s Version) (From The Vault), hasVaultStatus, From The Vault]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVaultStatus Context triple: [Suburban Legends (Taylor’s Version) (From The Vault), hasVaultStatus, From The Vault]
-
A.
hasVaultType
Indicates that an entity is associated with or classified by a particular type or category of vault.
-
B.
hasGoldVault
Indicates that one entity possesses or contains a vault specifically used for storing gold.
-
C.
hasReserveStatus
Indicates that an entity holds a designated reserve or backup status in relation to another entity or role.
-
D.
hasUnitStatus
Indicates that an entity is associated with a particular operational or condition status as a unit.
-
E.
vaultType
Indicates the specific category or classification of a vault associated with an entity or transaction.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de9a6f50208190b687b505f5cd1aa2 |
completed | April 14, 2026, 7:50 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:21 a.m.