Triple
T24592619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIBA Oceania Championship for Women |
E608575
|
entity |
| Predicate | usualFormat |
P59120
|
FINISHED |
| Object | round-robin |
—
|
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: round-robin | Statement: [FIBA Oceania Championship for Women, usualFormat, round-robin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usualFormat Context triple: [FIBA Oceania Championship for Women, usualFormat, round-robin]
-
A.
usedFormat
Indicates that one entity employs or applies a particular format or representation in relation to another entity.
-
B.
typicalUsageFormat
chosen
Indicates the usual or standard way in which something is expressed, presented, or formatted in practice.
-
C.
standardUse
Indicates that something is used in a typical, expected, or officially accepted manner for its intended purpose.
-
D.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
E.
standardFormUsedIn
Indicates that a particular standard form is employed or applied within a given context, process, or system.
- 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_69e2c4cf54248190af7b0c2d9ade9830 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9dc63208190b70f57b9821a7241 |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:30 a.m.