Triple
T35771739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nate Marquardt |
E1034179
|
entity |
| Predicate | hasNotableWinType |
P111111
|
FINISHED |
| Object | knockout victories |
—
|
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: knockout victories | Statement: [Nate Marquardt, hasNotableWinType, knockout victories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableWinType Context triple: [Nate Marquardt, hasNotableWinType, knockout victories]
-
A.
notableWinType
chosen
Indicates that the relationship specifies the particular category or type of a notable victory associated with an entity.
-
B.
notableWin
Indicates that one entity achieved a particularly significant or distinguished victory over another or in a specific event.
-
C.
hasNotableScore
Indicates that an entity is associated with a score or rating considered significant or noteworthy in its context.
-
D.
hasNotableSuccessIn
Indicates that an entity has achieved significant or widely recognized success in a particular field, activity, or domain.
-
E.
hasNotableRecord
Indicates that an entity possesses a distinguished or noteworthy achievement, performance, or documented accomplishment in some domain.
- 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_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.