Triple
T26473740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana Hoosiers |
E665969
|
entity |
| Predicate | foundedForAthletics |
P64655
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Indiana Hoosiers, foundedForAthletics, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedForAthletics Context triple: [Indiana Hoosiers, foundedForAthletics, late 19th century]
-
A.
foundedAsAthleticsProgram
chosen
Indicates that an organization or institution was originally established specifically as an athletics or sports program.
-
B.
sportGoverningFederationFoundedBy
Indicates that a sport governing federation was established or created by a specific person or organization.
-
C.
foundedFor
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
-
D.
foundedAsUniversityAthletics
Indicates that an athletics program was established at the same time as, and as an integral part of, the founding of a university.
-
E.
hasAthletics
Indicates that an entity participates in, is associated with, or offers athletics-related activities or programs.
- 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_69ee883f80dc819090e311b022b78e02 |
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:21 a.m.