Triple
T29629053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Madison Dukes football |
E755525
|
entity |
| Predicate | transitionToFBS |
P36477
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [James Madison Dukes football, transitionToFBS, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitionToFBS Context triple: [James Madison Dukes football, transitionToFBS, 2022]
-
A.
transitionTo
chosen
Indicates a change in state, condition, or phase from one defined status to another.
-
B.
transitionState
Indicates a change in condition or phase from one defined state to another within a process or system.
-
C.
formsTransitionBetween
Indicates that one state, phase, or condition serves as an intermediate link or bridge leading from one distinct state, phase, or condition to another.
-
D.
transitionStageBetween
Indicates a relationship where one state or phase serves as an intermediate or connecting stage between two other states or phases in a process or sequence.
-
E.
transitionReason
Indicates the cause, motivation, or triggering factor behind a change from one state, status, or condition to another.
- 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_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 28, 2026, 6:39 p.m.