Triple
T30910491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Long Time |
E787435
|
entity |
| Predicate | firstReleaseAsSingle |
P62507
|
FINISHED |
| Object | 1970 |
—
|
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: 1970 | Statement: [Long Long Time, firstReleaseAsSingle, 1970]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstReleaseAsSingle Context triple: [Long Long Time, firstReleaseAsSingle, 1970]
-
A.
firstReleasedAsSingleBy
Indicates that a musical work was first released in the form of a single by a specific artist or performer.
-
B.
firstReleasedAs
Indicates the original title or form under which an entity (such as a work, product, or version) was initially released before any later re-releases, renamings, or editions.
-
C.
firstRelease
Indicates that one entity is the initial or earliest release (in time or sequence) of another entity, such as a product, work, or version.
-
D.
releasedAsSingleIn
chosen
Indicates that a musical work or track was issued as a standalone single in a specific year or time period.
-
E.
firstAlbumSingleFrom
Indicates that one entity is the first single released from another entity’s album.
- 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0349d158b881908bfbdb501ea565ee |
completed | May 12, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_6a034750e3d48190a88ee3604a36b46d |
completed | May 12, 2026, 3:29 p.m. |
Created at: April 29, 2026, 8:50 p.m.