Triple
T26461403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Brazos |
E665646
|
entity |
| Predicate | reasonForDormancy |
P29551
|
FINISHED |
| Object | Texas A&M move to SEC in 2012 |
—
|
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: Texas A&M move to SEC in 2012 | Statement: [Battle of the Brazos, reasonForDormancy, Texas A&M move to SEC in 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForDormancy Context triple: [Battle of the Brazos, reasonForDormancy, Texas A&M move to SEC in 2012]
-
A.
inactivationReason
chosen
Indicates the reason or cause for which an entity, status, or process has been deactivated or made inactive.
-
B.
dormantAt
Indicates that an entity is in an inactive or non-operational state at a specified time or under certain conditions.
-
C.
dormancyPeriod
Indicates the length of time an entity remains inactive or in a dormant state before resuming activity.
-
D.
suspensionReason
Indicates the reason or cause for which an entity has been suspended from a status, activity, or service.
-
E.
isDormant
Indicates that an entity is currently inactive or in a resting state, with its usual functions or activities temporarily suspended.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 27, 2026, 12:12 a.m.