Triple
T24372228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trojans |
E614364
|
entity |
| Predicate | governsTeamsIn |
P143939
|
FINISHED |
| Object | men's sports |
—
|
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 sports | Statement: [Trojans, governsTeamsIn, men's sports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsTeamsIn Context triple: [Trojans, governsTeamsIn, men's sports]
-
A.
governingBodyOfOwnedTeam
Indicates that one entity serves as the governing or managing body responsible for overseeing and controlling the operations of a team that it owns.
-
B.
includesTeamsThat
chosen
Indicates that an entity contains or encompasses specific teams as part of its composition or scope.
-
C.
managedTeam
Indicates that one entity had responsibility for directing, supervising, and coordinating the work of another group or team.
-
D.
managedTeamLeague
Indicates that a person or organization had managerial responsibility for a team participating in a particular league.
-
E.
representsTeamsIn
Indicates that one entity serves as a representative or agent on behalf of a team or multiple teams.
- 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_69e2d7e1e010819098b95eb3f905943d |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293d462f88190bf95a83274d8a850 |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:02 a.m.