Triple
T8637131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huncho Jack, Jack Huncho |
E204549
|
entity |
| Predicate | featuresAdLibHeavyPerformances |
P69677
|
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: [Huncho Jack, Jack Huncho, featuresAdLibHeavyPerformances, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresAdLibHeavyPerformances Context triple: [Huncho Jack, Jack Huncho, featuresAdLibHeavyPerformances, true]
-
A.
featuresAdLibsBy
chosen
Indicates that something (such as a song or track) includes ad-lib vocal contributions performed by a specified artist or entity.
-
B.
featuresSoloPerformancesBy
Indicates that the subject includes or showcases solo performances carried out by the specified performer or performers.
-
C.
livePerformanceStapleFor
Indicates that something (such as a song or piece) is regularly and prominently featured in another entity’s live performances.
-
D.
livePerformanceFeature
Indicates that one entity is included or highlighted as a component of another entity’s live performance.
-
E.
performsMusicIn
Indicates that an entity presents or plays music within a particular venue, event, 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc47944d1c819081f448f14d04bf9d |
completed | March 31, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69cc455d6d448190a2da2a319ac78c37 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.