Triple
T17754604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | medieval University of Cambridge |
E443200
|
entity |
| Predicate | receivesRoyalCharters |
P4010
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [medieval University of Cambridge, receivesRoyalCharters, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesRoyalCharters Context triple: [medieval University of Cambridge, receivesRoyalCharters, true]
-
A.
hasRoyalCharter
chosen
Indicates that an entity has been formally granted a royal charter by a monarch or royal authority.
-
B.
royalWarrantGrantedIn
Indicates that an official royal warrant or authorization was granted in a specified place or jurisdiction.
-
C.
introducedLegalCharter
Indicates that an entity formally established or brought into effect a legal charter governing another entity or domain.
-
D.
hasRoyalWarrantFrom
Indicates that one party has been formally granted a royal warrant or official endorsement by a specific royal person or household.
-
E.
grantedRoyalPatronageBy
Indicates that an individual, group, or institution has officially received support, endorsement, or sponsorship from a member of a royal family.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4841da9988190b5efde3bbd3f24c3 |
completed | April 19, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:10 a.m.