Triple
T6849853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willie Pep |
E157987
|
entity |
| Predicate | competedInWeightClass |
P51164
|
FINISHED |
| Object | featherweight |
—
|
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 | Statement: [Willie Pep, competedInWeightClass, featherweight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competedInWeightClass Context triple: [Willie Pep, competedInWeightClass, featherweight]
-
A.
weightClass
Indicates the categorical grouping of an entity based on its weight range or mass classification.
-
B.
allowsWeightClasses
Indicates that one entity permits or supports the use of defined weight categories for another entity or within a given context.
-
C.
competitionWeight
Indicates the weight or importance assigned to an entity within a competitive context or event.
-
D.
competedAs
chosen
Indicates that an entity participated in a competition or contest in the role, category, or capacity specified by another entity.
-
E.
competedInDiscipline
Indicates that an entity took part in a competition or event within a specific discipline or category.
- 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d84acb288190a67d974197ecab2f |
completed | March 27, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69c6d0a12834819097d7e6c0b823745e |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:20 p.m.