Triple
T25355495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Flaco Explosivo |
E635809
|
entity |
| Predicate | weightClassesAssociated |
P8068
|
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: [El Flaco Explosivo, weightClassesAssociated, featherweight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weightClassesAssociated Context triple: [El Flaco Explosivo, weightClassesAssociated, featherweight]
-
A.
allowsWeightClasses
Indicates that one entity permits or supports the use of defined weight categories for another entity or within a given context.
-
B.
weightClass
chosen
Indicates the categorical grouping of an entity based on its weight range or mass classification.
-
C.
weightClassOrder
Indicates the relative ranking or sequence of entities based on their weight class, from lighter to heavier (or vice versa).
-
D.
weightClassAlternativeName
Indicates that one weight class is referred to by an alternative name or label.
-
E.
intendedUserWeightClass
Indicates the weight category or range for which a user is specifically targeted or intended.
- 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f49e0075b88190ba626e6591f24ed8 |
completed | May 1, 2026, 12:35 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:35 p.m.