Triple
T32638450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christ Church, Frederica |
E834413
|
entity |
| Predicate | parishEstablishedInCentury |
P75550
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Christ Church, Frederica, parishEstablishedInCentury, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parishEstablishedInCentury Context triple: [Christ Church, Frederica, parishEstablishedInCentury, 18th century]
-
A.
parishEstablished
Indicates that a parish was formally created or founded at a specific time or under specific authority.
-
B.
parishChurchCentury
chosen
Indicates the century during which a given parish church was established, built, or primarily dates from.
-
C.
parishFoundedBy
Indicates that a parish was established or created by a specific person or organization.
-
D.
parishChurchCompletedIn
Indicates the year or time period when a specific parish church was completed or finished being built.
-
E.
foundedInCentury
Indicates that an entity was established or came into existence 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_69f3492e773c81908afc10651e46cad3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c775d6188190b236fc4f89a11b61 |
completed | May 3, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:07 a.m.