Triple
T13778920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPC Athletics World Championships |
E331084
|
entity |
| Predicate | hasTeamRepresentation |
P102803
|
FINISHED |
| Object | national teams |
—
|
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: national teams | Statement: [IPC Athletics World Championships, hasTeamRepresentation, national teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTeamRepresentation Context triple: [IPC Athletics World Championships, hasTeamRepresentation, national teams]
-
A.
representsTeamFrom
Indicates that an entity serves as the representative team originating from or associated with a particular place, organization, or group.
-
B.
representedByTeam
Indicates that an entity is officially or formally represented by a specific team.
-
C.
hasTeamFor
chosen
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
-
D.
representsTeamsNamed
Indicates that two or more entities are associated with teams that share the same name.
-
E.
hasCityRepresented
Indicates that an entity (such as a representative or organization) is associated with or represents a specific city.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0239cbfc81909064ac2457fdfff5 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:11 p.m.