Triple
T5372621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gonville Court |
E108886
|
entity |
| Predicate | centralAreaOf |
P58897
|
FINISHED |
| Object | Gonville and Caius College |
—
|
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: Gonville and Caius College | Statement: [Gonville Court, centralAreaOf, Gonville and Caius College]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralAreaOf Context triple: [Gonville Court, centralAreaOf, Gonville and Caius College]
-
A.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
B.
coreAreaOf
chosen
Indicates that one entity is the central, primary, or most important area or domain of focus for another entity.
-
C.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
D.
centerType
Indicates the classification or category of a center (e.g., type of facility, institution, or hub) associated with an entity.
-
E.
centralName
Indicates that the specified name serves as the primary or main identifying label within a given context or naming structure.
- 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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.