Triple
T2795879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wakefield |
E53034
|
entity |
| Predicate | hasCathedralFeature |
P29783
|
FINISHED |
| Object | tall spire |
—
|
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: tall spire | Statement: [Wakefield, hasCathedralFeature, tall spire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCathedralFeature Context triple: [Wakefield, hasCathedralFeature, tall spire]
-
A.
containsCathedral
Indicates that one entity includes or has within its boundaries a cathedral associated with it.
-
B.
hasCathedralCity
Indicates that a particular city is officially recognized as the cathedral city associated with a given ecclesiastical jurisdiction or region.
-
C.
cathedralFeature
chosen
Indicates that one entity is a distinctive architectural or structural feature of a cathedral.
-
D.
hasCathedralStyle
Indicates that something possesses or is characterized by a particular architectural style associated with a cathedral.
-
E.
hasCathedralDiocese
Indicates that a cathedral is associated with or belongs to a particular diocese within a church’s administrative 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abddef754081908e6218dc2208e0fd |
completed | March 7, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69abdd040f9481908e9c7a2df88ea1ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.