Triple
T5078766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesus College Chapel |
E114461
|
entity |
| Predicate | primaryUseBy |
P40071
|
FINISHED |
| Object | members of Jesus College, Cambridge |
—
|
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: members of Jesus College, Cambridge | Statement: [Jesus College Chapel, primaryUseBy, members of Jesus College, Cambridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseBy Context triple: [Jesus College Chapel, primaryUseBy, members of Jesus College, Cambridge]
-
A.
primarilyUsedBy
chosen
Indicates that something is mainly or most commonly used by a particular entity or group.
-
B.
usedPrimarilyIn
Indicates that something is mainly or most commonly employed within a particular context, domain, or purpose.
-
C.
primaryUseInFeed
Indicates that something is the main or most common way an item is used or presented within a feed.
-
D.
mainlyUses
Indicates that one entity primarily relies on, employs, or utilizes another entity as its main tool, method, resource, or medium.
-
E.
primarilyFor
Indicates that something is mainly intended, designed, or used for a particular purpose, function, or beneficiary, even if it may have secondary uses.
- 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74f75cf0819088be9e076eaf3168 |
completed | March 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.