Triple
T36153102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC featherweight division |
E1045646
|
entity |
| Predicate | matchmakingAuthority |
P186505
|
FINISHED |
| Object | UFC matchmakers |
—
|
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: UFC matchmakers | Statement: [UFC featherweight division, matchmakingAuthority, UFC matchmakers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchmakingAuthority Context triple: [UFC featherweight division, matchmakingAuthority, UFC matchmakers]
-
A.
hasMatchmakingSystem
Indicates that an entity includes or is associated with a system that pairs or connects participants based on defined criteria.
-
B.
matchmaker
Indicates that one entity facilitates or arranges a romantic or marital relationship between two other entities.
-
C.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
D.
matches
Indicates that two entities correspond to or are in agreement with each other according to some defined criteria or pattern.
-
E.
decidingMatchFor
Indicates a relationship where one entity is chosen or determined as the appropriate or final match for another entity among possible alternatives.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:08 p.m.