Triple
T12297269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Someday We’ll Be Together |
E293119
|
entity |
| Predicate | isFinalSingleWithGroup |
P21957
|
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: [Someday We’ll Be Together, isFinalSingleWithGroup, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFinalSingleWithGroup Context triple: [Someday We’ll Be Together, isFinalSingleWithGroup, true]
-
A.
hasSingle
Indicates that an entity possesses exactly one instance of a specified related entity or attribute.
-
B.
isFollowUpToSingle
Indicates that one event, message, or action directly continues or responds to a single specific prior event, message, or action.
-
C.
isFinalEngagementOf
chosen
Indicates that a given engagement is the last or concluding engagement in a sequence or series of engagements involving the same entities.
-
D.
isBreakoutSingleOf
Indicates that a single is recognized as the breakout or first major hit release for an artist or group.
-
E.
isSoloPartFor
Indicates that something functions as an individual or standalone component within a larger whole or composition.
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:52 p.m.