Triple
T5992915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States 3x3 national basketball teams |
E133394
|
entity |
| Predicate | rulesVariantOf |
P67886
|
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: [United States 3x3 national basketball teams, rulesVariantOf, basketball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulesVariantOf Context triple: [United States 3x3 national basketball teams, rulesVariantOf, basketball]
-
A.
affectsVariant
Indicates that one entity has an influence or impact on a specific variant or version of another entity.
-
B.
usedInVariant
Indicates that something (such as a component, feature, or element) is utilized or included within a particular variant or version of a larger entity.
-
C.
laterVariantRole
Indicates that one role is a subsequent or later variant of another, reflecting a modified or evolved version of the original role.
-
D.
variant
Indicates that one entity is an alternative form, version, or variation of another entity.
-
E.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation 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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04e9189908190abc9c742b38dfabc |
completed | March 22, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04dbefd1081909795fe1a812b991a |
completed | March 22, 2026, 8:14 p.m. |
Created at: March 22, 2026, 4:05 p.m.