Triple
T31022671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIBA 3x3 Olympic tournament |
E790490
|
entity |
| Predicate | originOfRules |
P137413
|
FINISHED |
| Object | FIBA 3x3 Official Rules |
—
|
NE NERFINISHED |
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: FIBA 3x3 Official Rules | Statement: [FIBA 3x3 Olympic tournament, originOfRules, FIBA 3x3 Official Rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originOfRules Context triple: [FIBA 3x3 Olympic tournament, originOfRules, FIBA 3x3 Official Rules]
-
A.
lawOriginStory
Indicates the foundational narrative or circumstances that explain how a particular law came into existence.
-
B.
natureOfRule
Indicates the fundamental type or character of a rule, specifying what kind of rule it is or how it functions within a system.
-
C.
historicalOrigin
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
-
D.
describesOriginOf
chosen
Indicates that one entity specifies or explains the source, provenance, or origin of another entity.
-
E.
gameOfOrigin
Indicates the game from which an entity, such as a character, item, or concept, originally comes.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0079e152648190a9da2add94fc1831 |
completed | May 10, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_6a0078f77f9c8190af357a6016a2bd53 |
completed | May 10, 2026, 12:24 p.m. |
Created at: April 29, 2026, 8:58 p.m.