Triple
T37155110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European middleweight champion |
E920472
|
entity |
| Predicate | titleVacancyReason |
P156366
|
FINISHED |
| Object | loss in the ring |
—
|
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: loss in the ring | Statement: [European middleweight champion, titleVacancyReason, loss in the ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleVacancyReason Context triple: [European middleweight champion, titleVacancyReason, loss in the ring]
-
A.
reasonForLeaving
Indicates the cause, motivation, or circumstance that led an entity to depart or discontinue an association, position, or place.
-
B.
vacancyCondition
chosen
Indicates the condition or circumstances under which a position, role, or space is considered vacant.
-
C.
designationReason
Indicates the reason or justification for assigning a particular designation or status to an entity.
-
D.
reasonForTitle
Indicates the justification, cause, or basis for assigning a particular title to an entity.
-
E.
compensationReason
Indicates the reason or cause for which compensation is granted, requested, or applied between entities.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffcf46fd688190907fd1ceb499a8d1 |
completed | May 10, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69ffccde2a8c81908e055e74077dbd19 |
completed | May 10, 2026, 12:10 a.m. |
Created at: May 3, 2026, 4:15 p.m.