Triple
T7649469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Saints’ Church, Rothbury |
E173210
|
entity |
| Predicate | earliestFabricDate |
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: [All Saints’ Church, Rothbury, earliestFabricDate, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestFabricDate Context triple: [All Saints’ Church, Rothbury, earliestFabricDate, 13th century]
-
A.
earliestVersionDate
Indicates the date on which the earliest known or first version of an entity was created, released, or became valid.
-
B.
firstProducedAt
Indicates the location or context where something was originally created, manufactured, or brought into existence for the first time.
-
C.
earliestStrataDate
Indicates the earliest known or recorded date associated with a particular geological or archaeological stratum.
-
D.
fabricatedOn
Indicates that something was manufactured, constructed, or produced at a specific time or date.
-
E.
earliestDate
Indicates the earliest point in time at which an associated event, state, or relationship is considered to begin or be valid.
- F. None of above. chosen
Provenance (4 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_69c6995473348190a4f41d110d619a18 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7061cbc3c8190a917dd7e71214182 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015dd8fc8190bc5f52a12bd46209 |
completed | March 27, 2026, 10:14 p.m. |
| PDg | Predicate description generation | batch_69c7061b218c81909fff789ba4c10e58 |
completed | March 27, 2026, 10:35 p.m. |
Created at: March 27, 2026, 3:58 p.m.