Triple
T19519656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Émeute Maurice Richard |
E488369
|
entity |
| Predicate | seProduitPendant |
P136224
|
FINISHED |
| Object | saison 1954-1955 de la LNH |
—
|
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: saison 1954-1955 de la LNH | Statement: [Émeute Maurice Richard, seProduitPendant, saison 1954-1955 de la LNH]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seProduitPendant Context triple: [Émeute Maurice Richard, seProduitPendant, saison 1954-1955 de la LNH]
-
A.
byProduct
Indicates that one entity is produced incidentally or as a secondary result of a process, activity, or creation involving another entity.
-
B.
productFor
Indicates that one entity is intended to be used by, with, or in relation to another entity as its product or offering.
-
C.
producedOn
Indicates that something was created, manufactured, or brought into existence at a specific date or time.
-
D.
producedAs
Indicates that one entity is created, generated, or brought into existence as a result or output of another entity or process.
-
E.
indicationOfProduct
Indicates that something serves as evidence, a sign, or a marker pointing to the existence, presence, or relevance of a particular product.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6359edd508190afd68739de676ed7 |
completed | April 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7d0da88190aabf8b5799691fb1 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004d3a708190a1c13c8f644f3926 |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:40 p.m.