Triple
T21875010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shotti |
E540113
|
entity |
| Predicate | relationshipTo6ix9ine |
P146003
|
FINISHED |
| Object | business associate |
—
|
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: business associate | Statement: [Shotti, relationshipTo6ix9ine, business associate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipTo6ix9ine Context triple: [Shotti, relationshipTo6ix9ine, business associate]
-
A.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
B.
relationshipToPete
Indicates the specific type of relationship or connection that an entity has to Pete.
-
C.
relationshipToTheDude
Indicates the specific type of personal or social relationship that one entity has to the individual referred to as "the Dude."
-
D.
relationshipToJack
Indicates the specific type of personal or social connection an entity has with Jack.
-
E.
playerRelations
Indicates the nature or status of the relationship between players, such as alliances, rivalries, or other interpersonal dynamics.
- F. None of above. chosen
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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f33957f481908789b054a4fd1b77 |
completed | April 28, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 7:02 p.m.