Triple
T10120370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commonwealth Games men's doubles |
E223270
|
entity |
| Predicate | typicalDrawSize |
P81899
|
FINISHED |
| Object | 32 pairs |
—
|
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: 32 pairs | Statement: [Commonwealth Games men's doubles, typicalDrawSize, 32 pairs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDrawSize Context triple: [Commonwealth Games men's doubles, typicalDrawSize, 32 pairs]
-
A.
typicalDrawSizeDoubles
chosen
Indicates that the usual or standard size of the draw in a doubles event (e.g., in a tournament) has a specified number of participating teams.
-
B.
typicalDimension
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another entity.
-
C.
typicalWidth
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
-
D.
drawSizeSingles
Indicates the size or dimensions used when drawing a single item or element in a visual or graphical context.
-
E.
typicalPanelSize
Indicates the usual or standard dimensions associated with a given panel.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2659cdc8190b3ba91426bda55ec |
completed | April 2, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:04 p.m.