Triple
T26355486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Again (Lenny Kravitz music video) |
E663035
|
entity |
| Predicate | linkedToSingle |
P60695
|
FINISHED |
| Object | Again (Lenny Kravitz song) |
—
|
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: Again (Lenny Kravitz song) | Statement: [Again (Lenny Kravitz music video), linkedToSingle, Again (Lenny Kravitz song)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToSingle Context triple: [Again (Lenny Kravitz music video), linkedToSingle, Again (Lenny Kravitz song)]
-
A.
associatedSingle
chosen
Indicates a one-to-one association where an entity is linked to exactly one corresponding related entity.
-
B.
linkedByStructure
Indicates that two entities are connected or associated through a shared structural element, configuration, or framework.
-
C.
linkedToProperty
Indicates that one entity is associated or connected to a specific property or attribute of another entity.
-
D.
linkedToStatement
Indicates that one entity is associated or connected to a particular statement, typically as a reference, support, or contextual link.
-
E.
linkedPosition
Indicates that one position is associated or connected to another position in a defined way.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 26, 2026, 10:48 p.m.