Triple
T22192071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | College of DuPage athletic teams |
E548450
|
entity |
| Predicate | conferenceScope |
P146782
|
FINISHED |
| Object | regional |
—
|
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: regional | Statement: [College of DuPage athletic teams, conferenceScope, regional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceScope Context triple: [College of DuPage athletic teams, conferenceScope, regional]
-
A.
conferenceLevel
Indicates the competitive or organizational tier at which a conference or event is classified or held.
-
B.
publicationScope
Indicates the extent, audience, or boundaries within which something (such as a work, data, or information) is made publicly available or distributed.
-
C.
conferenceRecognition
Indicates that an entity has received recognition, such as an award, honor, or notable mention, in the context of a specific conference.
-
D.
conferenceType
Indicates the specific category or kind of conference associated with an entity (e.g., workshop, symposium, seminar).
-
E.
conference1
Indicates a relationship where an entity is associated with, participates in, or is characterized as a specific conference event or instance.
- 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12ae49ec881908fa42446b19e3f2d |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
| PDg | Predicate description generation | batch_69e7222e74248190a2d3671049f117f2 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:35 p.m.