Triple
T23165873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamarudeen Usman |
E578708
|
entity |
| Predicate | isNotablePersonIn |
P97477
|
FINISHED |
| Object | mixed martial arts |
—
|
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: mixed martial arts | Statement: [Kamarudeen Usman, isNotablePersonIn, mixed martial arts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotablePersonIn Context triple: [Kamarudeen Usman, isNotablePersonIn, mixed martial arts]
-
A.
namedForNotablePersonFrom
Indicates that one entity is named in honor of a notable person who originates from another specified place or group.
-
B.
hasNotablePeople
chosen
Indicates that certain people associated with an entity are distinguished or noteworthy in some recognized way.
-
C.
hasNotablePersonWithGivenName
Indicates that there exists a notable person associated with the subject whose given (first) name matches the specified value.
-
D.
notablePublicFigure
Indicates that the subject is widely recognized and holds a significant public profile or influence in society.
-
E.
hasNotablePersonAsFace
Indicates that an entity is publicly represented or symbolized by a specific notable person, such as a spokesperson, ambassador, or brand face.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f2bca4881909f6148d588948018 |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:03 p.m.