Triple
T16082549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tearin' Up My Heart |
E390143
|
entity |
| Predicate | followedBySingle |
P134
|
FINISHED |
| Object | Here We Go |
E1193184
|
NE 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: Here We Go | Statement: [Tearin' Up My Heart, followedBySingle, Here We Go]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Here We Go Context triple: [Tearin' Up My Heart, followedBySingle, Here We Go]
-
A.
Here We Go
chosen
"Here We Go" is an upbeat dance-pop song by American boy band *NSYNC, featured on their debut album and known for its catchy, high-energy style typical of late-1990s pop.
-
B.
Where We Go
"Where We Go" is a song by American singer Pink from her 2017 studio album *Beautiful Trauma*.
-
C.
Up We Go
"Up We Go" is a 2014 indie pop single by Canadian singer-songwriter Lights, known for its uplifting lyrics and anthemic, synth-driven sound.
-
D.
Where Do We Go
"Where Do We Go" is a song title that likely explores themes of uncertainty, direction, or searching for meaning.
-
E.
As We Go
As We Go is a collection of essays by American writer and editor Charles Dudley Warner, reflecting his observations on everyday life and society in the late 19th century.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1844b86288190ad0452aad6bdd5fb |
completed | April 17, 2026, 12:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff29bc7408190be09bec1619b599c |
completed | May 10, 2026, 2:51 a.m. |
Created at: April 10, 2026, 4:57 a.m.