Triple
T30654043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Último Guerrero |
E780335
|
entity |
| Predicate | hasWrestledIn |
P160432
|
FINISHED |
| Object | Mexico |
—
|
NE NERFINISHED |
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: Mexico | Statement: [Último Guerrero, hasWrestledIn, Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWrestledIn Context triple: [Último Guerrero, hasWrestledIn, Mexico]
-
A.
wrestledFor
Indicates that one entity engaged in a wrestling match or competition on behalf of, or as a representative of, another entity (such as a team, organization, or country).
-
B.
wrestledWith
Indicates that one entity engaged in a physical wrestling contest or struggle with another entity.
-
C.
wrestledForPromotion
Indicates that one entity engaged in a wrestling match or competitive struggle with another in order to gain a promotion or advancement.
-
D.
wrestledInCountry
chosen
Indicates that one entity participated in a wrestling match or wrestling activity within the geographical boundaries of a specified country.
-
E.
wrestlingPromotionAppearedIn
Indicates that a wrestler or wrestling-related entity made an appearance in a specific wrestling promotion or organization.
- 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a9a4d9081909d67b4dc73642cae |
completed | May 2, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:30 p.m.