Triple
T37506928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Illinois Panthers tennis |
E932117
|
entity |
| Predicate | governsMen |
P44518
|
FINISHED |
| Object | men's collegiate tennis |
—
|
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 collegiate tennis | Statement: [Eastern Illinois Panthers tennis, governsMen, men's collegiate tennis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsMen Context triple: [Eastern Illinois Panthers tennis, governsMen, men's collegiate tennis]
-
A.
governsGender
chosen
Indicates that one entity determines or constrains the gender classification or gender-related properties of another entity.
-
B.
governs
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
C.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
D.
governsRoleOf
Indicates that one entity has authority or control over the role, responsibilities, or functions assigned to another entity.
-
E.
areGovernedBy
Indicates that one or more entities are under the authority, control, or administration of a governing body or ruler.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0352b6c7dc81908f190060eb1e1857 |
completed | May 12, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_6a03507c37d4819091068b2ec5cacef9 |
completed | May 12, 2026, 4:08 p.m. |
Created at: May 3, 2026, 4:17 p.m.