Triple
T24766099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vuyani Bungu |
E619586
|
entity |
| Predicate | movedUpInWeightTo |
P157294
|
FINISHED |
| Object | featherweight division |
—
|
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: featherweight division | Statement: [Vuyani Bungu, movedUpInWeightTo, featherweight division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movedUpInWeightTo Context triple: [Vuyani Bungu, movedUpInWeightTo, featherweight division]
-
A.
movedFor
Indicates that one entity changed its location or position for the benefit, purpose, or in response to another entity.
-
B.
movedBy
Indicates that an entity changes position or location as a result of another entity’s action or influence.
-
C.
movedOn
Indicates that an entity changed its position or location from one place to another at some point in time.
-
D.
changesRankOf
Indicates a relationship where one entity causes or effects a change in the rank or hierarchical position of another entity.
-
E.
ascendedTo
Indicates that one entity rose, climbed, or moved upward to reach the position, level, or location of another entity.
- F. None of above. chosen
Provenance (4 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f42b11251881908070b93355de64ad |
completed | May 1, 2026, 4:24 a.m. |
Created at: April 18, 2026, 4:28 a.m.