Triple
T9681238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Will Remember You |
E234285
|
entity |
| Predicate | notableVersionType |
P89602
|
FINISHED |
| Object | live recording |
—
|
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: live recording | Statement: [I Will Remember You, notableVersionType, live recording]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVersionType Context triple: [I Will Remember You, notableVersionType, live recording]
-
A.
notableRelease
Indicates that an entity is a significant or prominent release (such as a major version, edition, or launch) associated with another entity.
-
B.
hasNotableVersion
Indicates that an entity has a specific version or variant that is particularly significant, distinguished, or noteworthy compared to other versions.
-
C.
notableLiveVersion
Indicates that one work is a particularly significant or well-known live performance version of another work.
-
D.
notableTargetType
Indicates that the subject is notable or significant specifically in relation to entities of the given target type.
-
E.
notableBranch
Indicates that one entity is a particularly significant or prominent subdivision, offshoot, or branch of another entity.
- 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_69ca84c99e34819092e5563a7106cfca |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9c9fec1c8190b2626848cb2c1871 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:16 p.m.