Triple
T38635095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congregation of Jesus |
E937555
|
entity |
| Predicate | countryOfFounder |
P203550
|
FINISHED |
| Object | England |
E1791
|
NE 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: England | Statement: [Congregation of Jesus, countryOfFounder, England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfFounder Context triple: [Congregation of Jesus, countryOfFounder, England]
-
A.
countryOfOriginOfFounder
chosen
Indicates the country from which the founder of an entity originates.
-
B.
foundingLocationPresentCountry
Indicates the present-day country in which the location where something (typically an organization or institution) was founded is situated.
-
C.
homeCountryDuringFounding
Indicates the country in which an entity (such as an organization or company) was based at the time it was founded.
-
D.
historicalOriginCountry
Indicates the country from which something originally came or first emerged in a historical context.
-
E.
countryOfEponym
Indicates that the related entity is named after something (an eponym) originating from or associated with a particular country.
- F. None of above.
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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a421581a0d48190a32d948c4d3a1888 |
completed | June 29, 2026, 6:49 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.