Triple
T31023291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Cervera |
E790504
|
entity |
| Predicate | notableUseAfterClosure |
—
|
GENERATED |
| Object | secondary education institution |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableUseAfterClosure Context triple: [University of Cervera, notableUseAfterClosure, secondary education institution]
-
A.
notableClosure
Indicates that an entity is recognized for a significant or noteworthy ending, shutdown, or termination event.
-
B.
operatorAfterClosure
Indicates that one operator entity occurs or is applied after the completion or closure of another operator or process.
-
C.
closureUse
Indicates that one entity makes use of another entity within a closure, typically capturing it from an enclosing scope for later execution.
-
D.
closureUse
Indicates that one entity uses or captures another entity within a closure context (such as a variable or resource referenced by a closure).
-
E.
conditionAfterClosure
Indicates the state or circumstances that exist after a process, event, or entity has been formally closed or concluded.
- F. None of above. chosen
Provenance (1 batch)
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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:58 p.m.