Triple
T34578715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Griz |
E887830
|
entity |
| Predicate | fullProgramName |
P152750
|
FINISHED |
| Object | Montana Grizzlies football |
—
|
NE NERFINISHED |
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: Montana Grizzlies football | Statement: [Griz, fullProgramName, Montana Grizzlies football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullProgramName Context triple: [Griz, fullProgramName, Montana Grizzlies football]
-
A.
programFullName
chosen
Indicates the complete, official name of a program as opposed to an abbreviation or short title.
-
B.
defaultProgramName
Indicates the standard or pre-selected name assigned to a program when no specific name is explicitly provided.
-
C.
nicknameOfProgram
Indicates that one name is used as an informal or alternative nickname for a particular program.
-
D.
programmeName
Indicates that an entity has or is identified by a specific programme’s name.
-
E.
programOf
Indicates that one entity is a program (such as a course of study or curriculum) that is offered, managed, or associated with another entity (such as an institution, department, or organization).
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7209b45e48190b08a5085d90865e5 |
completed | May 3, 2026, 10:16 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:03 a.m.