Triple
T22318777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University Interscholastic League |
E551723
|
entity |
| Predicate | academicEventsInclude |
P147724
|
FINISHED |
| Object | debate |
—
|
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: debate | Statement: [University Interscholastic League, academicEventsInclude, debate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: academicEventsInclude Context triple: [University Interscholastic League, academicEventsInclude, debate]
-
A.
academicCalendar
Indicates the schedule or structure of academic terms, sessions, and key dates associated with an educational institution or program.
-
B.
academicConference
Indicates a relationship where an event functions as an academic conference, typically involving scholarly presentations, discussions, and exchanges among researchers or professionals.
-
C.
conferenceSince
Indicates that a conference-related relationship or interaction between entities has been in effect continuously since a specified point in time.
-
D.
conferencesCovered
Indicates that one entity has reported on, documented, or provided coverage of one or more conferences associated with another entity.
-
E.
individualEvents
Indicates that the subject is associated with one or more distinct, separately identifiable events rather than a single aggregated or continuous occurrence.
- F. None of above. chosen
Provenance (4 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15762fac08190a6a514baffbbbca1 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:42 p.m.