Triple
T22381055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of St Bene't |
E553272
|
entity |
| Predicate | continuouslyInUseSince |
P2935
|
FINISHED |
| Object | early medieval 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: early medieval period | Statement: [Church of St Bene't, continuouslyInUseSince, early medieval period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuouslyInUseSince Context triple: [Church of St Bene't, continuouslyInUseSince, early medieval period]
-
A.
inUseSince
Indicates that an entity has been actively in use starting from a specified point in time.
-
B.
usedSince
chosen
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
-
C.
areUsedSince
Indicates that entities have been in use continuously starting from a specified point in time.
-
D.
durationOfUse
Indicates the length of time for which something is used or remains in use.
-
E.
maintainedSince
Indicates that an entity has been kept in a particular state or condition continuously from a specified point in time onward.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1582c05fc8190836ae008426177a5 |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.