Triple
T7814805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Martin's Church, Canterbury |
E180977
|
entity |
| Predicate | hasOriginsIn |
P3654
|
FINISHED |
| Object | late Roman period |
—
|
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: late Roman period | Statement: [St Martin's Church, Canterbury, hasOriginsIn, late Roman period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginsIn Context triple: [St Martin's Church, Canterbury, hasOriginsIn, late Roman period]
-
A.
hasOriginIn
chosen
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
B.
hasOriginFeature
Indicates that an entity possesses a specific characteristic, attribute, or feature related to its origin or source.
-
C.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
D.
hasHierarchyIn
Indicates that one entity occupies a higher or lower level within an ordered structure or chain of command relative to another entity in a specified context.
-
E.
alternativeOrigin
Indicates that an entity has a different or secondary source, starting point, or provenance compared to its primary or usual origin.
- 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_69ca828153f48190bdb27ac46f8e0745 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf96c009c81909726e1653b6f1348 |
completed | March 30, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:39 p.m.