Triple
T1861173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Hockey League |
E34814
|
entity |
| Predicate | hadHomeAndAwayGames |
P8330
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [International Hockey League, hadHomeAndAwayGames, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadHomeAndAwayGames Context triple: [International Hockey League, hadHomeAndAwayGames, true]
-
A.
playedHomeGamesFrom
Indicates the time period during which a team or player hosted their home games at a particular venue.
-
B.
playedHomeGamesUntil
Indicates the period up to which a team or player hosted their home games at a particular venue.
-
C.
homeAndAwayMatchesPerTeam
Indicates that each team plays a specified number of matches both at their home venue and at their opponent’s venue.
-
D.
homeAndAwayFormat
chosen
Indicates that a competition or matchup is structured so that each pair of opponents plays twice, once at each participant’s home venue and once away.
-
E.
playedHomeMatchesIn
Indicates that an entity (typically a sports team) hosted its home matches at a specified venue or location.
- 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_69a88600b2f88190bc09303e68ab517e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abb16c09e48190a345c95eab59fd87 |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe02c3c819093a4744b476106ca |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.