Triple
T35527254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBJJF Brazilian jiu-jitsu competitions |
E1026704
|
entity |
| Predicate | allowVictoryCondition |
P20842
|
FINISHED |
| Object | submission |
—
|
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: submission | Statement: [IBJJF Brazilian jiu-jitsu competitions, allowVictoryCondition, submission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowVictoryCondition Context triple: [IBJJF Brazilian jiu-jitsu competitions, allowVictoryCondition, submission]
-
A.
conditionOfVictory
chosen
Indicates the specific circumstances or criteria under which a participant is considered to have won.
-
B.
victoryIn
Indicates that one entity achieves a win or success in a specific contest, event, or competitive context involving another entity.
-
C.
typeOfVictory
Indicates the specific manner or category in which a victory was achieved.
-
D.
victoryTarget
Indicates that one entity is the intended opponent, objective, or condition that must be overcome or achieved for the other entity to attain victory.
-
E.
hasVictoryLane
Indicates that a racing event, track, or venue includes or is associated with a designated victory lane area where winners are celebrated.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 3, 2026, 4:04 p.m.