Triple
T26298594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pretty Boy |
E661485
|
entity |
| Predicate | bearerStatus |
P164202
|
FINISHED |
| Object | undefeated world champion |
—
|
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: undefeated world champion | Statement: [Pretty Boy, bearerStatus, undefeated world champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerStatus Context triple: [Pretty Boy, bearerStatus, undefeated world champion]
-
A.
bearerStance
Indicates the attitude, position, or viewpoint that the bearer holds toward a referenced subject or issue.
-
B.
bearer
Indicates that one entity carries, holds, or possesses another entity, often as the current holder of a right, document, or object.
-
C.
bearerFounded
Indicates that the bearer (such as a person or organization) is the one who established or created the associated entity (such as a company, institution, or project).
-
D.
bearerHandedness
Indicates the handedness (e.g., left, right, ambidextrous) associated with the bearer in the described relationship or context.
-
E.
bandStatus
Indicates the current operational or lifecycle state of a band (e.g., active, on hiatus, disbanded).
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f643c204508190a43fe0ec5165b01c |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 26, 2026, 10:14 p.m.