Triple
T21411601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ripon |
E528183
|
entity |
| Predicate | hasCathedralCityStatusSince |
P21120
|
FINISHED |
| Object | medieval period |
—
|
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: medieval period | Statement: [Ripon, hasCathedralCityStatusSince, medieval period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCathedralCityStatusSince Context triple: [Ripon, hasCathedralCityStatusSince, medieval period]
-
A.
hasCathedralStatusSince
chosen
Indicates the point in time from which something has held the official status of a cathedral.
-
B.
hasCoCathedralStatusSince
Indicates that an entity has held the status of a co-cathedral starting from a specified point in time.
-
C.
hasCathedralStatusGrantedBy
Indicates that cathedral status has been formally conferred on something (typically a church or building) by a specified granting authority.
-
D.
hasCathedralCity
Indicates that a particular city is officially recognized as the cathedral city associated with a given ecclesiastical jurisdiction or region.
-
E.
hasCathedralTown
Indicates that a given town is recognized as having a cathedral, typically serving as the seat of a bishop or central church authority.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b1fe2cd08190bfaf28daae4f5233 |
completed | April 22, 2026, 11:33 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:43 p.m.