Triple
T20546177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Wilfrid’s Church, Mobberley |
E504474
|
entity |
| Predicate | dateOfEarliestFabric |
P78561
|
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: [St Wilfrid’s Church, Mobberley, dateOfEarliestFabric, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfEarliestFabric Context triple: [St Wilfrid’s Church, Mobberley, dateOfEarliestFabric, 13th century]
-
A.
earliestFabricDate
chosen
Indicates the earliest date at which the fabric (or material) associated with an entity was created or first produced.
-
B.
earliestFindsDateTo
Indicates the earliest known date at which the finding, discovery, or observation of one entity is recorded as relating to another entity.
-
C.
earliestStrataDate
Indicates the earliest known or recorded date associated with a particular geological or archaeological stratum.
-
D.
artifactsDatedTo
Indicates that certain artifacts have been assigned or associated with a specific date or time period.
-
E.
earliestDocumentsDate
Indicates the earliest date on which the associated documents were created, recorded, or became valid.
- 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_69e0b4b52c048190952b4d0f430813a3 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a298630c8190993d53fc27eb3aec |
completed | April 20, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:38 a.m.