Triple
T38218080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eagles |
E1010738
|
entity |
| Predicate | governsTeamsAtLevel |
P36085
|
FINISHED |
| Object | varsity |
—
|
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: varsity | Statement: [Eagles, governsTeamsAtLevel, varsity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsTeamsAtLevel Context triple: [Eagles, governsTeamsAtLevel, varsity]
-
A.
supportsTeamLevel
Indicates that one entity provides assistance, resources, or endorsement to a team as a whole rather than to individual members.
-
B.
controlsTeamLevel
Indicates that one entity has authority or decision-making power over the overall direction, strategy, or functioning of a team.
-
C.
governsSportLevel
Indicates that one entity has authority to set, control, or regulate the competitive level or tier at which a sport or sporting activity is conducted.
-
D.
sportsTeamLevel
chosen
Indicates the competitive tier or division in which a sports team participates within an organized league or system.
-
E.
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.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.