Triple
T24944518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | minimumweight |
E624149
|
entity |
| Predicate | rankingMaintainedBy |
P4846
|
FINISHED |
| Object | World Boxing Organization |
—
|
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: World Boxing Organization | Statement: [minimumweight, rankingMaintainedBy, World Boxing Organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingMaintainedBy Context triple: [minimumweight, rankingMaintainedBy, World Boxing Organization]
-
A.
rankedBy
chosen
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
B.
rankingBasis
Indicates the criterion or standard used to determine the order or rank of entities in a ranking.
-
C.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
D.
rankedAs
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
-
E.
maintainsRanking
Indicates that one entity preserves or keeps another entity’s position or level within a ranking or ordered list.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 18, 2026, 5:53 a.m.