Triple
T17704777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge May Bumps |
E441401
|
entity |
| Predicate | heldInTerm |
P49722
|
FINISHED |
| Object | Easter term |
—
|
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: Easter term | Statement: [Cambridge May Bumps, heldInTerm, Easter term]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldInTerm Context triple: [Cambridge May Bumps, heldInTerm, Easter term]
-
A.
hasAcademicTerm
chosen
Indicates the relationship between an educational program, course, or institution and the specific academic term (e.g., semester, quarter, or session) during which it occurs or is valid.
-
B.
holdsIn
Indicates that a relationship, condition, or event is valid or occurs within a specified time interval or temporal context.
-
C.
areHeldIn
Indicates that events, activities, or objects take place or are located within a particular venue, container, or setting.
-
D.
holdsAt
Indicates that a particular condition or fluent is true and persists at a specified point in time.
-
E.
heldOn
Indicates that an event or activity takes place at a specific time, date, or occasion.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47296770c8190b6b172fb647da564 |
completed | April 19, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:05 a.m.