Triple
T35527259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBJJF Brazilian jiu-jitsu competitions |
E1026704
|
entity |
| Predicate | includeScoringAction |
P10576
|
FINISHED |
| Object | takedown |
—
|
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: takedown | Statement: [IBJJF Brazilian jiu-jitsu competitions, includeScoringAction, takedown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeScoringAction Context triple: [IBJJF Brazilian jiu-jitsu competitions, includeScoringAction, takedown]
-
A.
includesScoreFor
Indicates that one entity contains or accounts for the score associated with another entity.
-
B.
includesScoreBy
Indicates that one entity’s overall score or evaluation incorporates or is partly determined by the score assigned by another entity.
-
C.
usesScoringVector
Indicates that one entity evaluates or ranks another entity by applying a specific scoring vector or weighted set of criteria.
-
D.
includesNewScoreBy
Indicates that an entity incorporates or contains a newly added score produced by another entity.
-
E.
scoring
chosen
Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
- 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_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.