Triple
T24691437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regent Square Church |
E611447
|
entity |
| Predicate | primaryCenturyOfProminence |
P94236
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Regent Square Church, primaryCenturyOfProminence, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCenturyOfProminence Context triple: [Regent Square Church, primaryCenturyOfProminence, 19th century]
-
A.
popularInCentury
Indicates that something was widely liked, influential, or commonly recognized during a specified century.
-
B.
notableFromCentury
chosen
Indicates that an entity is notably associated with, or best known from, a particular century.
-
C.
originalCentury
Indicates the century in which something was originally created, produced, or came into existence.
-
D.
latestCentury
Indicates that the associated time or event occurs in, or belongs to, the most recent century relative to a given reference point.
-
E.
emergedByCentury
Indicates that something came into existence, became prominent, or first appeared during a specified century.
- 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 3:20 a.m.