Triple
T34766392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jean-Marc Mormeck |
E1002226
|
entity |
| Predicate | laterCompetedIn |
P51164
|
FINISHED |
| Object | heavyweight division |
—
|
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: heavyweight division | Statement: [Jean-Marc Mormeck, laterCompetedIn, heavyweight division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCompetedIn Context triple: [Jean-Marc Mormeck, laterCompetedIn, heavyweight division]
-
A.
competedAs
chosen
Indicates that an entity participated in a competition or contest in the role, category, or capacity specified by another entity.
-
B.
regionCompetedIn
Indicates the geographic region or area where an entity participated in a competition or contest.
-
C.
competedFor
Indicates that an entity took part in a contest, rivalry, or competition in pursuit of another entity (such as a prize, position, or resource).
-
D.
hasCompetitionHistory
Indicates that an entity has a recorded history of participation in competitions or competitive events.
-
E.
previouslyCompetedAsPartOf
Indicates that an entity once participated in a competition or event as a member or component of another entity, but no longer does so.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a0042524d8c8190884a10fce669ae95 |
completed | May 10, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_6a0041e89bd881909e32764699bcb89b |
completed | May 10, 2026, 8:29 a.m. |
Created at: May 3, 2026, 3:59 p.m.