Triple
T1188394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazilian jiu-jitsu |
E25299
|
entity |
| Predicate | hasHigherRankBelts |
P17947
|
FINISHED |
| Object | coral 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: coral belt | Statement: [Brazilian jiu-jitsu, hasHigherRankBelts, coral belt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHigherRankBelts Context triple: [Brazilian jiu-jitsu, hasHigherRankBelts, coral belt]
-
A.
hasBlackBeltIn
Indicates that an entity holds a black belt rank or equivalent high-level certification in a specified martial art or discipline.
-
B.
hasRankCategory
Indicates that an entity is assigned to a particular rank-based classification or level within an ordered hierarchy.
-
C.
usesBeltSystem
Indicates that a subject employs a structured belt-ranking system (e.g., colored belts) to denote levels of skill, progress, or status.
-
D.
typicallyHoldsRank
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
-
E.
hasRankOrder
chosen
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd568cf481908d10cf19a3ce28f3 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5bacc481909e8dfd5215e4711a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.