Triple
T13481035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBO heavyweight title |
E318370
|
entity |
| Predicate | judgingSystem |
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: [WBO heavyweight title, judgingSystem, 10-point must system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judgingSystem Context triple: [WBO heavyweight title, judgingSystem, 10-point must system]
-
A.
judgedBy
Indicates that one entity evaluates, assesses, or forms an opinion about another entity, often in an official or critical capacity.
-
B.
judgedOn
Indicates that an entity is evaluated or assessed based on a specified criterion, standard, or aspect.
-
C.
judgedAs
Indicates that one entity evaluates or forms an opinion about another entity according to some criteria or standard.
-
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.
judgesMayBe
Indicates that certain individuals can serve in the role of judges under specified conditions or classifications.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf36c6b08190ba99400600e0b662 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.