Triple
T16423379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto Professionals |
E398877
|
entity |
| Predicate | usedProfessionalPlayers |
P27786
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Toronto Professionals, usedProfessionalPlayers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedProfessionalPlayers Context triple: [Toronto Professionals, usedProfessionalPlayers, true]
-
A.
hasProfessionalPlayers
chosen
Indicates that an entity is associated with or includes individuals who participate in a profession at a professional level.
-
B.
introducedProfessionalPlayers
Indicates that one entity caused or facilitated the first professional appearance or involvement of certain players in a professional context.
-
C.
professionalPlayersAllowedFrom
Indicates that professional players are permitted to participate starting from a specified point, such as a date, level, or stage.
-
D.
hasPlayedProfessionalSports
Indicates that an entity has participated as an athlete in an officially recognized professional-level sports competition or league.
-
E.
primaryUseByPlayers
Indicates the main way in which players typically use or interact with the referenced entity.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328f911b88190b19de52a1f700af8 |
completed | April 18, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.