Triple
T36402617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Andrew’s Church, Kegworth |
E896669
|
entity |
| Predicate | naveDate |
P185441
|
FINISHED |
| Object | 14th 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: 14th century | Statement: [St Andrew’s Church, Kegworth, naveDate, 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: naveDate Context triple: [St Andrew’s Church, Kegworth, naveDate, 14th century]
-
A.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
B.
date
Indicates that two entities are engaged in or participate in a romantic or social outing or relationship with each other.
-
C.
visionDate
Indicates the date on which a particular vision, plan, or conceptual idea was created, recorded, or formally established.
-
D.
dateOfJourney
Indicates the specific calendar date on which a particular journey or trip takes place.
-
E.
titleDate
Indicates the date associated with a title, such as when it was granted, recorded, or became effective.
- 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:10 p.m.