Triple
T18392554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St James the Great Church, South Leigh |
E449770
|
entity |
| Predicate | hasLaterAdditionsFrom |
P110135
|
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 James the Great Church, South Leigh, hasLaterAdditionsFrom, 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterAdditionsFrom Context triple: [St James the Great Church, South Leigh, hasLaterAdditionsFrom, 14th century]
-
A.
laterAdditionsBy
chosen
Indicates that one entity consists of or represents additions or modifications that were made to another entity at a later time.
-
B.
laterIncludedOn
Indicates that one entity was added to, incorporated into, or featured on another entity at a subsequent time.
-
C.
laterEditionContains
Indicates that a later edition of a work includes all or part of the content from an earlier edition.
-
D.
hasAdditionalArticlesSince
Indicates that an entity has gained one or more new articles since a specified prior point in time or state.
-
E.
introducedAfter
Indicates that one entity was introduced at a later time or stage than another entity.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e518435cf481908393c1eb2b4ba659 |
completed | April 19, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.