Triple
T32934820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commonwealth Games men's singles |
E842496
|
entity |
| Predicate | drawSeparatedBy |
P175418
|
FINISHED |
| Object | seeding |
—
|
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: seeding | Statement: [Commonwealth Games men's singles, drawSeparatedBy, seeding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drawSeparatedBy Context triple: [Commonwealth Games men's singles, drawSeparatedBy, seeding]
-
A.
separatesBy
Indicates that one entity divides, partitions, or creates a boundary between two or more other entities.
-
B.
separatedIn
Indicates that two or more entities, once together or associated, have been divided, split, or otherwise placed into distinct parts, groups, or locations.
-
C.
definedSeparationFrom
Indicates a formally specified distinction or boundary established between one entity and another.
-
D.
separatedInto
Indicates that something has been divided or split into distinct parts, groups, or components.
-
E.
separatedFromSerialBy
Indicates that one entity is positioned with a serial element (such as a serial number or serial identifier) acting as a separator between it and 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: May 1, 2026, 1:20 a.m.