Triple
T16404339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Table Tennis Championships |
E398385
|
entity |
| Predicate | separatedTeamEventsFrom |
P12217
|
FINISHED |
| Object | individual events |
—
|
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: individual events | Statement: [World Table Tennis Championships, separatedTeamEventsFrom, individual events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatedTeamEventsFrom Context triple: [World Table Tennis Championships, separatedTeamEventsFrom, individual events]
-
A.
separatedInto
chosen
Indicates that something has been divided or split into distinct parts, groups, or components.
-
B.
teamDuringEvent
Indicates that a particular team is associated with, participates in, or is active during a specified event.
-
C.
separatedIn
Indicates that two or more entities, once together or associated, have been divided, split, or otherwise placed into distinct parts, groups, or locations.
-
D.
teamParticipatedIn
Indicates that a team took part in or was involved in a particular event, activity, or competition.
-
E.
teamsParticipated
Indicates that the referenced teams took part in a particular event, activity, or competition.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327d1f16481909adb19dab86dcc72 |
completed | April 18, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.