Triple
T13446151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan national 3x3 basketball teams |
E320487
|
entity |
| Predicate | playsVariantOf |
P109968
|
FINISHED |
| Object | basketball |
—
|
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: basketball | Statement: [Japan national 3x3 basketball teams, playsVariantOf, basketball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsVariantOf Context triple: [Japan national 3x3 basketball teams, playsVariantOf, basketball]
-
A.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
-
B.
rulesVariantOf
Indicates that one set of rules is a modified or alternative version derived from another set of rules.
-
C.
scriptVariantOf
Indicates that one script is a variant or alternative form of another script, typically differing in style, region, or historical development while remaining closely related.
-
D.
likelyVariantOf
Indicates that one entity is probably a variant, version, or alternative form of another entity, based on available evidence or similarity.
-
E.
famousVariant
Indicates that one entity is a well-known or widely recognized version or form of another entity.
- F. None of above. chosen
Provenance (4 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaef5f610819092cad33ef72075ff |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:40 p.m.