Triple
T29146176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000 NHL All-Star Game |
E738779
|
entity |
| Predicate | notableFormatNote |
P14840
|
FINISHED |
| Object | continued North America vs. World format introduced in late 1990s |
—
|
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: continued North America vs. World format introduced in late 1990s | Statement: [2000 NHL All-Star Game, notableFormatNote, continued North America vs. World format introduced in late 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFormatNote Context triple: [2000 NHL All-Star Game, notableFormatNote, continued North America vs. World format introduced in late 1990s]
-
A.
notableFormat
chosen
Indicates that something is particularly recognized or distinguished for being in a specific format.
-
B.
notableDisplay
Indicates that something is prominently or distinctively presented in a way that draws special attention or recognition.
-
C.
notableEdition
Indicates that a particular edition or version of a work is especially significant or noteworthy in relation to that work.
-
D.
notableReader
Indicates that the subject is recognized as a particularly significant or distinguished reader of the object.
-
E.
notedIn
Indicates that information about one entity is mentioned, recorded, or referenced within another entity, such as a document, record, or source.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a0308a4591081909018e2ba5d70096e |
completed | May 12, 2026, 11:01 a.m. |
| PD | Predicate disambiguation | batch_6a03079299708190a2ecaf14d3f06f48 |
completed | May 12, 2026, 10:57 a.m. |
Created at: April 28, 2026, 11:39 a.m.