Triple
T8073874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Pancras Old Church |
E188442
|
entity |
| Predicate | claimedFoundationDate |
P80349
|
FINISHED |
| Object | early Christian era |
—
|
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 Christian era | Statement: [St Pancras Old Church, claimedFoundationDate, early Christian era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedFoundationDate Context triple: [St Pancras Old Church, claimedFoundationDate, early Christian era]
-
A.
reFoundationDate
Indicates the date on which an entity was re-established or founded again after a previous foundation.
-
B.
foundedAt
Indicates the time or date at which an entity (such as an organization, project, or institution) was established or created.
-
C.
foundedOn
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
-
D.
issuerFoundedAs
Indicates that the issuer was originally established or created under a particular prior name, form, or organizational identity.
-
E.
claimsFoundationBy
Indicates that one entity asserts or declares that another entity serves as its basis, origin, or underlying foundation.
- 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_69ca82b50c708190863f661d438e68df |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb404a98408190b6c8eecb95ad086d |
completed | March 31, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:27 p.m.