Triple
T35771736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nate Marquardt |
E1034179
|
entity |
| Predicate | competedForOrganization |
P32080
|
FINISHED |
| Object | UFC |
—
|
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 | Statement: [Nate Marquardt, competedForOrganization, UFC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competedForOrganization Context triple: [Nate Marquardt, competedForOrganization, UFC]
-
A.
competedFor
chosen
Indicates that an entity took part in a contest, rivalry, or competition in pursuit of another entity (such as a prize, position, or resource).
-
B.
competedAs
Indicates that an entity participated in a competition or contest in the role, category, or capacity specified by another entity.
-
C.
previouslyCompetedAsPartOf
Indicates that an entity once participated in a competition or event as a member or component of another entity, but no longer does so.
-
D.
competeIn
Indicates that an entity takes part as a contender in a particular event, activity, or domain where performance is compared against others.
-
E.
competitionOrganization
Indicates that an organization is responsible for organizing, hosting, or managing a competition or contest.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 3, 2026, 4:06 p.m.