Triple
T22916229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazilian National Jiu-Jitsu Championship |
E568739
|
entity |
| Predicate | hasBeltLevel |
P18146
|
FINISHED |
| Object | white belt |
—
|
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: white belt | Statement: [Brazilian National Jiu-Jitsu Championship, hasBeltLevel, white belt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeltLevel Context triple: [Brazilian National Jiu-Jitsu Championship, hasBeltLevel, white belt]
-
A.
hasPhysicalBelt
Indicates that one entity possesses or is equipped with a physical belt as an item or feature.
-
B.
usesBeltSystem
chosen
Indicates that a subject employs a structured belt-ranking system (e.g., colored belts) to denote levels of skill, progress, or status.
-
C.
hasGreenBeltStatus
Indicates that an entity holds a recognized "green belt" level or certification within a defined ranking or qualification system.
-
D.
hasCommuterBelt
Indicates that one area functions as the commuter belt for another, meaning people regularly travel from the first area to the second for work or daily activities.
-
E.
beltType
Indicates the specific kind or category of belt associated with an 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18079217481908db98882929ac69a |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.