Triple
T29629068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Madison Dukes football |
E755525
|
entity |
| Predicate | formerProgramLevel |
P21470
|
FINISHED |
| Object | Football Championship Subdivision |
—
|
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: Football Championship Subdivision | Statement: [James Madison Dukes football, formerProgramLevel, Football Championship Subdivision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerProgramLevel Context triple: [James Madison Dukes football, formerProgramLevel, Football Championship Subdivision]
-
A.
formerProgram
Indicates that an entity previously held the role or status of a program but no longer does so.
-
B.
programLevel
chosen
Indicates the hierarchical or categorical level at which a program is defined or operates (e.g., undergraduate, graduate, or other tiers).
-
C.
originProgram
Indicates the program, initiative, or source project from which an entity, item, or record originally comes.
-
D.
implementedProgram
Indicates that an entity has created, developed, or put into operation a particular program or software system.
-
E.
laterUsedForProgram
Indicates that something is subsequently utilized as part of, or as input to, a program or programming process.
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: April 28, 2026, 6:39 p.m.