Triple
T5929576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Letterkenny Irish |
E131900
|
entity |
| Predicate | teamIdentity |
P7598
|
FINISHED |
| Object | Irish-themed junior hockey team in Letterkenny |
—
|
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: Irish-themed junior hockey team in Letterkenny | Statement: [Letterkenny Irish, teamIdentity, Irish-themed junior hockey team in Letterkenny]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamIdentity Context triple: [Letterkenny Irish, teamIdentity, Irish-themed junior hockey team in Letterkenny]
-
A.
associatedTeamName
Indicates the name of the team that is linked or connected to a given entity.
-
B.
teamName
chosen
Indicates the relationship that assigns or associates a specific name with a particular team.
-
C.
teamRepresentation
Indicates that one entity serves as the official representative or embodiment of a team in a given context or activity.
-
D.
team1Franchise
Indicates that an entity serves as or represents the franchise associated with the first team in a given sports or competitive context.
-
E.
leagueTeam2
Indicates that the subject entity is the second team participating in a particular league, matchup, or league-related context.
- 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_69c0085b75e88190a632f9691f9da48b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c033541d108190a34d1fde2fe9dacb |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4 p.m.