Triple
T31914847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke Blue Devils men's lacrosse |
E814799
|
entity |
| Predicate | varsityStatusStartYear |
P68600
|
FINISHED |
| Object | 1949 |
—
|
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: 1949 | Statement: [Duke Blue Devils men's lacrosse, varsityStatusStartYear, 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: varsityStatusStartYear Context triple: [Duke Blue Devils men's lacrosse, varsityStatusStartYear, 1949]
-
A.
establishedAsVarsityProgram
chosen
Indicates that an athletic or academic program was officially recognized and elevated to full varsity status within an institution.
-
B.
fullCollegeStatusYear
Indicates the year in which an entity attained or was recognized with full college status.
-
C.
previousStatusBeforeVarsity
Indicates the status or condition an entity had immediately before entering or being associated with varsity.
-
D.
yearOfCommencement
Indicates the specific year in which an activity, event, project, or entity officially began or was initiated.
-
E.
typicalAcademicYearStart
Indicates the usual calendar date or period when an academic year customarily begins for an institution or system.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b1eceb6c8190bc7775c0fe4c26eb |
completed | May 3, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: May 1, 2026, 12:02 a.m.