Triple
T31315170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We Were Happy (Taylor’s Version) (From The Vault) |
E798573
|
entity |
| Predicate | fromRecord |
P87306
|
FINISHED |
| Object | Fearless (Taylor’s Version) |
—
|
NE NERFINISHED |
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: Fearless (Taylor’s Version) | Statement: [We Were Happy (Taylor’s Version) (From The Vault), fromRecord, Fearless (Taylor’s Version)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fromRecord Context triple: [We Were Happy (Taylor’s Version) (From The Vault), fromRecord, Fearless (Taylor’s Version)]
-
A.
setRecordFor
Indicates establishing or updating a specific record associated with an entity or context.
-
B.
reRecordedFrom
chosen
Indicates that one recording is a new recording derived from, based on, or made again from an earlier recording.
-
C.
formerRecord
Indicates that an entity previously held a particular record or status but no longer does so.
-
D.
isRecord
Indicates that one entity functions as an official or authoritative record of another entity or of some information.
-
E.
referentRecord
Indicates that one record serves as a reference or pointer to another record within a data or information structure.
- 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_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:15 p.m.