Triple
T31454446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Men's Team Championships |
E802411
|
entity |
| Predicate | matchTypesIncluded |
P93204
|
FINISHED |
| Object | men's singles |
—
|
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: men's singles | Statement: [World Men's Team Championships, matchTypesIncluded, men's singles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchTypesIncluded Context triple: [World Men's Team Championships, matchTypesIncluded, men's singles]
-
A.
matchTypes
Indicates that two or more entities share the same type or category according to a specified classification.
-
B.
includesMatchType
chosen
Indicates that one entity’s set or collection contains an element with a specified type of match (e.g., exact, partial, or pattern-based) to another entity.
-
C.
matchesType
Indicates that one entity has the same or a compatible type as another entity according to a defined type system or classification.
-
D.
includesMatch
Indicates that one entity contains or encompasses a particular match or matching instance of another entity.
-
E.
matchType
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:15 p.m.