Triple
T37290343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TUC |
E925647
|
entity |
| Predicate | associatedWithLeagueTier |
P50168
|
FINISHED |
| Object | AHL |
E1559475
|
NE 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: AHL | Statement: [TUC, associatedWithLeagueTier, AHL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithLeagueTier Context triple: [TUC, associatedWithLeagueTier, AHL]
-
A.
associatedWithLeagueThroughTeam
Indicates that an entity is connected to a sports league indirectly by being part of, or represented by, a team that belongs to that league.
-
B.
associatedLeagueLevel
chosen
Indicates that one entity is linked to another entity representing the competitive tier or level of a sports league.
-
C.
associatedWithCompetitionLevel
Indicates that something has a relationship to, or is characterized by, a particular level or tier of competition.
-
D.
affiliateLeague
Indicates that one sports organization or team is formally associated with and operates under the umbrella or partnership of a particular league.
-
E.
athleticAssociationTier
Indicates the competitive level or division within an athletic association to which an entity (such as a team or institution) belongs.
- F. None of above.
Provenance (4 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_69f76eb0f86c819098dee07393e69ec3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40514203e08190a7b067d8785076d7 |
completed | June 27, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.