Triple
T396458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Shakespeare Theater |
E8992
|
entity |
| Predicate | hasEducationalAudience |
P12602
|
FINISHED |
| Object | students |
—
|
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: students | Statement: [Chicago Shakespeare Theater, hasEducationalAudience, students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEducationalAudience Context triple: [Chicago Shakespeare Theater, hasEducationalAudience, students]
-
A.
hasEducationalRole
Indicates that an entity holds a specific function, position, or responsibility within an educational context or setting.
-
B.
hasEducationalMission
Indicates that an entity is responsible for or engaged in carrying out an educational purpose, goal, or function.
-
C.
hasEducationalProgram
Indicates that an entity offers, runs, or is associated with a specific educational program.
-
D.
educationalFocus
Indicates the primary subject area or theme that an educational activity, program, or resource is centered on.
-
E.
containsEducationalInstitution
Indicates that one entity geographically or administratively includes or encompasses an educational institution within its boundaries or structure.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec8a941081909a152fda0ce24a98 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96bd3848190a66ca14dfbd26da5 |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ea7d03a88190aab72e61d8673488 |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.