Triple
T193330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of England |
E3765
|
entity |
| Predicate | founderRole |
P7059
|
FINISHED |
| Object | initiated by Henry VIII |
—
|
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: initiated by Henry VIII | Statement: [Church of England, founderRole, initiated by Henry VIII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: founderRole Context triple: [Church of England, founderRole, initiated by Henry VIII]
-
A.
founder
Indicates that an entity established, created, or started another entity such as an organization, institution, or company.
-
B.
cofounderOf
Indicates that a person jointly established or created an organization, company, or project with one or more other founders.
-
C.
foundingMember
Indicates that an entity is one of the original creators or initial participants involved in establishing another entity, such as an organization, group, or project.
-
D.
coFounderWith
Indicates that two or more entities jointly founded the same organization or venture.
-
E.
foundedWith
Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a2596810c48190ab687c0c2efaa9e2 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a256769ad8819083c1d83082c0215e |
completed | Feb. 28, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69a2582b7f648190b0ef676b8bdc1c65 |
completed | Feb. 28, 2026, 2:51 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.