Triple
T23038588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyokushin karate |
E573674
|
entity |
| Predicate | competitionCharacteristic |
P150748
|
FINISHED |
| Object | no punches to the head with bare fists |
—
|
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: no punches to the head with bare fists | Statement: [Kyokushin karate, competitionCharacteristic, no punches to the head with bare fists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionCharacteristic Context triple: [Kyokushin karate, competitionCharacteristic, no punches to the head with bare fists]
-
A.
notableLeagueCharacteristic
Indicates that a particular characteristic is especially prominent or defining for a given league.
-
B.
competitionSurface
Indicates the type of surface or medium on which a competition or contest takes place.
-
C.
competitionRole
Indicates that an entity holds a specific role, position, or function within a competitive event or contest.
-
D.
rivalryFeature
Indicates a competitive or adversarial relationship between entities, often characterized by ongoing opposition or comparison.
-
E.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f185121da0819095b523d7d2c923ab |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:53 p.m.