Triple
T13699978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Man of Tai Chi |
E328489
|
entity |
| Predicate | hasFightTournament |
P111218
|
FINISHED |
| Object | underground fighting 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: underground fighting ring | Statement: [Man of Tai Chi, hasFightTournament, underground fighting ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFightTournament Context triple: [Man of Tai Chi, hasFightTournament, underground fighting ring]
-
A.
hasTournament
Indicates that an entity organizes, hosts, or is associated with a specific tournament.
-
B.
hasFight
Indicates that one entity engages in a physical or verbal conflict with another entity.
-
C.
hasTournamentRecord
Indicates that an entity possesses a documented performance or results record in a specific tournament or set of tournaments.
-
D.
playedInTournament
Indicates that an entity participated as a competitor or player in a specific tournament.
-
E.
hasFoughtInPromotion
Indicates that an entity (such as a fighter) has participated in at least one fight under a specific promotion or fighting organization.
- F. None of above. chosen
Provenance (4 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc879adc88190b03f1cf815b71061 |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:54 p.m.