Triple
T21843588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tui shou |
E539316
|
entity |
| Predicate | hasCompetitionForm |
P26034
|
FINISHED |
| Object | push hands tournaments |
—
|
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: push hands tournaments | Statement: [Tui shou, hasCompetitionForm, push hands tournaments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetitionForm Context triple: [Tui shou, hasCompetitionForm, push hands tournaments]
-
A.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
B.
hasCompetitionElement
chosen
Indicates that one entity includes, involves, or is associated with a specific competitive component, aspect, or feature.
-
C.
hasCompetitionContext
Indicates that an entity is associated with or occurs within a specific competitive setting, event, or environment.
-
D.
formedForCompetition
Indicates that an entity was created or organized specifically to participate in a competition.
-
E.
tieneCompetencia
Indicates that one entity has or faces competition from another entity.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0bd5248f08190ba208512eafbe7ad |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.