Triple
T23038538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Master IBJJF Jiu-Jitsu Championship |
E573673
|
entity |
| Predicate | hasTeamScoring |
P29024
|
FINISHED |
| Object | academy points |
—
|
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: academy points | Statement: [World Master IBJJF Jiu-Jitsu Championship, hasTeamScoring, academy points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTeamScoring Context triple: [World Master IBJJF Jiu-Jitsu Championship, hasTeamScoring, academy points]
-
A.
teamScoring
chosen
Indicates that a team achieves a score or points in a game, match, or competitive event.
-
B.
topTryScorerTeam
Indicates that a team is the one for which a given player is the top try scorer.
-
C.
hasScoreSystem
Indicates that an entity uses, is governed by, or is associated with a particular scoring or rating system.
-
D.
decidingScoreTeam
Indicates the team whose score ultimately determines the outcome or winner in a game or match.
-
E.
hasScorer
Indicates that one entity serves as the scorer (e.g., the one who scores points, goals, or evaluations) in relation to another 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_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. |
Created at: April 17, 2026, 3:53 p.m.