Triple
T3820504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UAB Blazers football team |
E84359
|
entity |
| Predicate | programReinstated |
P18106
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [UAB Blazers football team, programReinstated, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programReinstated Context triple: [UAB Blazers football team, programReinstated, 2017]
-
A.
reconstructionProgram
Indicates a program or initiative designed to rebuild, restore, or structurally improve something that has been damaged, degraded, or is otherwise in need of renewal.
-
B.
implementedProgram
Indicates that an entity has created, developed, or put into operation a particular program or software system.
-
C.
programOn
Indicates that a program is scheduled to be broadcast or presented on a particular channel, station, platform, or device.
-
D.
reintroduced
chosen
Indicates that an entity that was previously removed, extinct, or absent has been brought back or restored to a place, context, or state.
-
E.
establishedProgram
Indicates that an entity has created and put into operation a formal program that is now in an active, ongoing state.
- 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_69aed931f5908190be2c07af66d4df25 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee74a2bc081909b237df8b1e27653 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.