Triple
T5116752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penryn |
E115353
|
entity |
| Predicate | grantedBoroughStatus |
P58209
|
FINISHED |
| Object | 13th century |
—
|
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: 13th century | Statement: [Penryn, grantedBoroughStatus, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedBoroughStatus Context triple: [Penryn, grantedBoroughStatus, 13th century]
-
A.
hadBoroughStatus
Indicates that an entity previously possessed the official status or designation of a borough.
-
B.
hadBoroughStatusFrom
chosen
Indicates that an entity held the legal or administrative status of a borough starting from a specified point in time.
-
C.
grantedStatus
Indicates that an entity has been officially approved or given a particular status, permission, or privilege.
-
D.
cityStatusGrantedBy
Indicates that one entity (such as a person, authority, or institution) formally granted or conferred city status upon another entity (typically a settlement or locality).
-
E.
hasBorough
Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75cfa9f88190aa7dfd264e554899 |
completed | March 20, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69bd7160d44081908cc64f3c14d28b81 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.