Triple
T31493092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilary term |
E803458
|
entity |
| Predicate | hasAlternativeInOtherUniversities |
P155778
|
FINISHED |
| Object | Lent term |
—
|
NE NERFINISHED |
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: Lent term | Statement: [Hilary term, hasAlternativeInOtherUniversities, Lent term]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeInOtherUniversities Context triple: [Hilary term, hasAlternativeInOtherUniversities, Lent term]
-
A.
hasUniversities
Indicates that an entity possesses, contains, or is associated with one or more universities.
-
B.
hasUniversityBranch
Indicates that an institution maintains an official branch or satellite campus of a university at a given location or within another organization.
-
C.
hasAdditionalCampus
Indicates that an educational institution maintains one or more campuses in addition to its primary or main campus.
-
D.
hasSiblingCampus
Indicates that one campus is recognized as a sibling or peer campus of another within the same institution or organizational network.
-
E.
hasAlternativeProgram
chosen
Indicates that one program is an alternative option or substitute for another program.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 30, 2026, 9:39 p.m.