Triple
T29068862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Daddy |
E735757
|
entity |
| Predicate | hasPerformerNotableAlias |
P84992
|
FINISHED |
| Object | El Jefe |
—
|
NE NERFINISHED |
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: El Jefe | Statement: [King Daddy, hasPerformerNotableAlias, El Jefe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformerNotableAlias Context triple: [King Daddy, hasPerformerNotableAlias, El Jefe]
-
A.
hasMusicalAlias
chosen
Indicates that an entity is known or performs under an alternative musical name or stage name.
-
B.
hasPerformerGivenName
Indicates that a performer is associated with a specific given (first) name.
-
C.
hasNotablePerformer
Indicates that an entity features or is associated with a performer who is particularly prominent, famous, or otherwise noteworthy.
-
D.
hasPerformerLabelAssociation
Indicates a relationship linking a performer to an associated label, such as a record label or organizational affiliation.
-
E.
associatedWithArtistNickname
Indicates that an entity is connected to or identified by a particular artist’s nickname or pseudonym.
- 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 28, 2026, 10:19 a.m.