Triple
T22238589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of England |
E549656
|
entity |
| Predicate | foundingDateApproximate |
P69762
|
FINISHED |
| Object | 1530s |
—
|
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: 1530s | Statement: [Church of England, foundingDateApproximate, 1530s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingDateApproximate Context triple: [Church of England, foundingDateApproximate, 1530s]
-
A.
foundedInYearApprox
Indicates that an entity was established or came into existence around an approximate year, rather than on a precisely known date.
-
B.
foundingAround
chosen
Indicates that an entity was founded at approximately, but not exactly, the specified time or within a loosely defined surrounding period.
-
C.
isFoundedOn
Indicates that one entity is established, created, or based upon another entity as its foundational source or principle.
-
D.
foundedOn
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
-
E.
foundedBefore
Indicates that one entity was established or created at an earlier time than the other entity.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f132123a048190ba5a90d7acb9aeb2 |
completed | April 28, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:38 p.m.