Triple
T36708756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sisters of St. Paul of Chartres |
E906735
|
entity |
| Predicate | motherhouseLocation |
P101932
|
FINISHED |
| Object | Chartres |
—
|
NE NERFINISHED |
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: Chartres | Statement: [Sisters of St. Paul of Chartres, motherhouseLocation, Chartres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motherhouseLocation Context triple: [Sisters of St. Paul of Chartres, motherhouseLocation, Chartres]
-
A.
motherhouseOf
Indicates that one religious community or congregation serves as the principal or founding house (central residence and administrative center) of another related community.
-
B.
motherChurch
Indicates that one church serves as the primary, founding, or supervising church in relation to another church.
-
C.
hasMotherhouseLocation
chosen
Indicates the location where an organization’s primary or founding house (motherhouse) is situated.
-
D.
foundedAsConventFor
Indicates that an institution or building was originally established specifically to serve as a convent for a particular religious community or group.
-
E.
foundingLocationOfChurch
Indicates the place where a particular church was originally founded or established.
- 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c81113f88190af2bf0f86492a064 |
completed | May 3, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.