Triple
T25368300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan national rugby union team |
E632862
|
entity |
| Predicate | worldRugbyRankingBestPosition |
P112975
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [Japan national rugby union team, worldRugbyRankingBestPosition, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldRugbyRankingBestPosition Context triple: [Japan national rugby union team, worldRugbyRankingBestPosition, 8]
-
A.
worldRugbyRankingBest
Indicates that the subject entity holds the highest (best) position in the World Rugby rankings among the compared entities.
-
B.
worldRugbyRankingsBestRank
chosen
Indicates the highest (best) position an entity has ever achieved in the World Rugby rankings.
-
C.
worldRugbyRankingSystem
Indicates a ranking relationship where entities are ordered or evaluated according to the World Rugby ranking system.
-
D.
worldRugbyRankingBestYear
Indicates the year in which an entity achieved its highest position in the World Rugby rankings.
-
E.
representsInWorldRugby
Indicates that an entity serves as an official representative or member within the organizational structure of World Rugby.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 21, 2026, 1:38 p.m.