Triple
T289879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fellow of Jesus College, Cambridge |
E5965
|
entity |
| Predicate | mayHold |
P9417
|
FINISHED |
| Object | university office |
—
|
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: university office | Statement: [Fellow of Jesus College, Cambridge, mayHold, university office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayHold Context triple: [Fellow of Jesus College, Cambridge, mayHold, university office]
-
A.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
-
B.
mayExtendTo
Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
-
C.
holding
Indicates that one entity is physically grasping, carrying, or keeping another entity in its possession or control.
-
D.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
-
E.
heldThat
Indicates that an entity (often a person or authority) maintained, asserted, or concluded that a particular proposition or judgment is true.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e4df5508190ab75115ac6b3964e |
completed | Feb. 28, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69a25b7d089081909810442c3d0182f6 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25d0ec71081908478c800be4f7bb0 |
completed | Feb. 28, 2026, 3:12 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.