Triple
T29024777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huncho |
E737557
|
entity |
| Predicate | hasMainAssociatedPerson |
P134996
|
FINISHED |
| Object | Quavo |
—
|
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: Quavo | Statement: [Huncho, hasMainAssociatedPerson, Quavo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainAssociatedPerson Context triple: [Huncho, hasMainAssociatedPerson, Quavo]
-
A.
hasMainRepresentative
Indicates that one entity serves as the primary or official representative of another entity.
-
B.
leaderAssociatedWith
Indicates a relationship where a leader is connected or affiliated with a particular entity, such as an organization, group, or cause.
-
C.
associatedPersonField
chosen
Indicates that there is a person linked or connected to the subject in a relevant or contextual way.
-
D.
hasMainOrganizationRole
Indicates that an entity holds the primary or most significant organizational role within a given context or structure.
-
E.
hasPersona
Indicates that an entity possesses or is associated with a particular persona, role, or character profile.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: April 28, 2026, 9:51 a.m.