Triple
T30898816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Find a Way |
E787101
|
entity |
| Predicate | isPopCrossoverHit |
P56239
|
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: [Find a Way, isPopCrossoverHit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPopCrossoverHit Context triple: [Find a Way, isPopCrossoverHit, true]
-
A.
hasCrossoverHits
Indicates that an entity (such as an artist or work) has achieved significant success across multiple distinct genres, markets, or audience categories.
-
B.
crossoverHit
chosen
Indicates that a creative work has achieved significant popularity or success across multiple distinct audience segments, genres, or markets beyond its original target.
-
C.
isMajorHit
Indicates that something (such as a work, product, or performance) has achieved a high level of success, popularity, or impact.
-
D.
isEarlyHitFor
Indicates that one entity is an initial or precursor success, discovery, or recognition that occurs early in relation to another entity.
-
E.
isMajorHitIn
Indicates that a work (such as a song, film, or product) achieved major commercial success or popularity within a specified market, region, or context.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6923d7438819088dfc308d1e22fd0 |
completed | May 3, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:50 p.m.