Triple
T1188506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC Welterweight division |
E25301
|
entity |
| Predicate | scoringSystem |
P16816
|
FINISHED |
| Object | 10-point must system |
—
|
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: 10-point must system | Statement: [UFC Welterweight division, scoringSystem, 10-point must system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoringSystem Context triple: [UFC Welterweight division, scoringSystem, 10-point must system]
-
A.
scoring
Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
-
B.
scoreScale
Indicates the scale or range on which a score or rating is expressed or measured.
-
C.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
D.
ratingSystem
chosen
Indicates a system or method used to assign evaluative scores or rankings to items, actions, or entities based on defined criteria.
-
E.
topTryScorer
Indicates that the subject is the player who scored the highest number of tries in a given competition, season, or context.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd568cf481908d10cf19a3ce28f3 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5bacc481909e8dfd5215e4711a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.