Triple
T17729024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hold On Tight |
E442539
|
entity |
| Predicate | hasChorusLanguageMix |
P70288
|
FINISHED |
| Object | English and French |
—
|
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: English and French | Statement: [Hold On Tight, hasChorusLanguageMix, English and French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChorusLanguageMix Context triple: [Hold On Tight, hasChorusLanguageMix, English and French]
-
A.
hasChorusLanguage
chosen
Indicates that the language used in the chorus section of a work (such as a song or musical piece) is a specified language.
-
B.
hasChorusIn
Indicates that a musical work includes a chorus section within the specified part or segment.
-
C.
hasChorus
Indicates that something (typically a song or musical piece) includes a chorus section as part of its structure.
-
D.
hasChorusBy
Indicates that something (typically a musical work or song) includes a chorus section that is performed, written, or provided by a specified entity.
-
E.
hasChorusStyle
Indicates that an entity is associated with a particular style or manner in which a chorus is performed or structured.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e478e4ae5c8190a6f0743f7e74b5bf |
completed | April 19, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:08 a.m.