Triple
T16970263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wyvern College (former) |
E411651
|
entity |
| Predicate | closureOrReorganization |
P50589
|
FINISHED |
| Object | closed or reorganized prior to present day |
—
|
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: closed or reorganized prior to present day | Statement: [Wyvern College (former), closureOrReorganization, closed or reorganized prior to present day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closureOrReorganization Context triple: [Wyvern College (former), closureOrReorganization, closed or reorganized prior to present day]
-
A.
closureReason
Indicates the reason or cause for which an entity, process, or case has been closed or terminated.
-
B.
closureProcess
Indicates the procedure or set of actions carried out to formally conclude, finalize, or terminate an ongoing activity, case, or process.
-
C.
closureBy
Indicates that one entity causes, performs, or is responsible for the closing or termination of another entity, event, or process.
-
D.
closure
chosen
Indicates that an entity is closed or not accessible/available for use, entry, or interaction.
-
E.
closureCompleted
Indicates that a previously initiated closure process or shutdown has been fully and successfully completed.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0ac23a48190992fa125fceb1eb2 |
completed | April 18, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:31 a.m.