Triple
T20562901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1976–77 Montreal Canadiens |
E504888
|
entity |
| Predicate | homeRecord |
P140566
|
FINISHED |
| Object | 33–1–6 |
—
|
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: 33–1–6 | Statement: [1976–77 Montreal Canadiens, homeRecord, 33–1–6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeRecord Context triple: [1976–77 Montreal Canadiens, homeRecord, 33–1–6]
-
A.
homeScore
Indicates the number of points or goals scored by the home team or home participant in a game or match.
-
B.
homeTo
Indicates that a place serves as the primary location, residence, or habitat for a person, group, or thing.
-
C.
homeBaseOf
Indicates that a particular place serves as the primary location, headquarters, or main operational base for an entity.
-
D.
homeOrAway
Indicates whether an entity is acting in its own location (home) or in another’s location (away) within a given context.
-
E.
homeDome
Indicates that one entity serves as the home arena or stadium (often a domed venue) for another entity, such as a sports team.
- F. None of above. chosen
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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a79f906c819081163de9649ccb17 |
completed | April 20, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:39 a.m.