Triple
T23371559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Now That We Found Love |
E593486
|
entity |
| Predicate | danceHit |
P152458
|
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: [Now That We Found Love, danceHit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danceHit Context triple: [Now That We Found Love, danceHit, true]
-
A.
danceFeature
Indicates that one entity serves as a notable characteristic, element, or attribute of a dance or dancing-related activity.
-
B.
danceHall
Indicates a relationship where a location functions as a dance hall, i.e., a place designated or used for dancing activities or dance events.
-
C.
danceBackground
Indicates that one entity serves as the background or setting for another entity’s dancing activity.
-
D.
musicAndDance
Indicates a relationship where music is performed, accompanied by, or integrated with dance as a coordinated activity or event.
-
E.
danceShow
Indicates that one entity presents or performs a dance-related show or performance for another or for an audience.
- F. None of above. chosen
Provenance (4 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3af45ec8190a32aa4e5f04f6756 |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 5:32 p.m.