Triple
T20994206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I've Never Been in Love Before |
E517103
|
entity |
| Predicate | originallyDuet |
P9649
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [I've Never Been in Love Before, originallyDuet, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyDuet Context triple: [I've Never Been in Love Before, originallyDuet, true]
-
A.
originalSong
Indicates that one entity is the source or initial version of a song from which another entity (such as a cover, remix, or adaptation) is derived.
-
B.
hasVocalDuet
chosen
Indicates that two entities perform or participate together in a vocal duet.
-
C.
originallyIn
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
-
D.
usesOriginalVocalsFrom
Indicates that one work incorporates the original, unaltered vocal recordings from another work.
-
E.
originallyInstrumental
Indicates that an entity was initially used as the instrument or means by which an action or effect was brought about, especially when this instrumental role may have changed over time.
- 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc1e75188190a97114238ea0b4f9 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:50 p.m.