Triple
T3940424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Court, Queens’ College, Cambridge |
E92019
|
entity |
| Predicate | isCentralCourtyardOf |
P10828
|
FINISHED |
| Object | Queens’ College, Cambridge |
—
|
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: Queens’ College, Cambridge | Statement: [Old Court, Queens’ College, Cambridge, isCentralCourtyardOf, Queens’ College, Cambridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCentralCourtyardOf Context triple: [Old Court, Queens’ College, Cambridge, isCentralCourtyardOf, Queens’ College, Cambridge]
-
A.
hasCourtyard
chosen
Indicates that one entity includes, features, or is characterized by the presence of a courtyard.
-
B.
courtyardName
Indicates that an entity has a specific name assigned to a courtyard.
-
C.
hasCourtyardArea
Indicates that an entity includes or is associated with a courtyard and specifies the size or extent of that courtyard space.
-
D.
isMainBuildingOf
Indicates that a building serves as the primary or central facility associated with a particular organization, complex, or site.
-
E.
courtyardShape
Indicates the geometric form or configuration that characterizes a courtyard.
- 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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedfc88e4819084adefb695b975c5 |
completed | March 9, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.