Triple
T24688768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European heavyweight title |
E611371
|
entity |
| Predicate | belt |
P108536
|
FINISHED |
| Object | championship belt awarded to the titleholder |
—
|
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: championship belt awarded to the titleholder | Statement: [European heavyweight title, belt, championship belt awarded to the titleholder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belt Context triple: [European heavyweight title, belt, championship belt awarded to the titleholder]
-
A.
beltType
Indicates the specific kind or category of belt associated with an entity.
-
B.
beltFunction
Indicates the functional role or purpose that a belt serves in relation to another object or system.
-
C.
beltMaterial
Indicates the material from which a belt is made.
-
D.
beltPosition
Indicates the relative placement or alignment of a belt with respect to another object or reference point.
-
E.
beltRepresents
chosen
Indicates that a belt symbolizes, signifies, or stands for a particular concept, status, or meaning in a given context.
- 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:19 a.m.