Triple
T29069483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iluminatti |
E735773
|
entity |
| Predicate | performerFeatured |
P10644
|
FINISHED |
| Object | Romeo Santos |
E227573
|
NE 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: Romeo Santos | Statement: [Iluminatti, performerFeatured, Romeo Santos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerFeatured Context triple: [Iluminatti, performerFeatured, Romeo Santos]
-
A.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
-
B.
hasFeaturedArtist
chosen
Indicates that an entity (such as a song or track) includes another artist who appears as a featured performer.
-
C.
featuredSongPerformancesFrom
Indicates that certain song performances are highlighted or prominently presented as originating from a particular source, event, or context.
-
D.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
-
E.
featuresSoloPerformancesBy
Indicates that the subject includes or showcases solo performances carried out by the specified performer or performers.
- F. None of above.
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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a276ece7c9081909458864374c24fa9 |
completed | June 9, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 28, 2026, 10:19 a.m.