Triple
T13693339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatfield College Rugby Team |
E328319
|
entity |
| Predicate | playsForLeagueLevel |
P50168
|
FINISHED |
| Object | college level |
—
|
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: college level | Statement: [Hatfield College Rugby Team, playsForLeagueLevel, college level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsForLeagueLevel Context triple: [Hatfield College Rugby Team, playsForLeagueLevel, college level]
-
A.
associatedLeagueLevel
chosen
Indicates that one entity is linked to another entity representing the competitive tier or level of a sports league.
-
B.
stateLeagueLevel
Indicates the competitive tier or division level of a league within a particular state’s league system.
-
C.
developmentLeagueFor
Indicates that one entity serves as a developmental or minor league affiliate for another, typically higher-level, sports team or organization.
-
D.
eligibleLeague
Indicates that an entity (such as a team or player) is qualified or permitted to participate in a particular league.
-
E.
leagueType
Indicates the classification or category of a league within a broader organizational or competitive structure.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc8757b648190a26181efbad09a43 |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.