Triple
T14091498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congregation of the Sacred Hearts of Jesus and Mary |
E339142
|
entity |
| Predicate | genderBranches |
P112781
|
FINISHED |
| Object | male branch |
—
|
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: male branch | Statement: [Congregation of the Sacred Hearts of Jesus and Mary, genderBranches, male branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderBranches Context triple: [Congregation of the Sacred Hearts of Jesus and Mary, genderBranches, male branch]
-
A.
femaleBranch
Indicates that one entity is a female branch or female-line subdivision of another entity within a hierarchical or genealogical structure.
-
B.
genderCategories
Indicates the classification of an entity into one or more gender-related categories or identities.
-
C.
genderDivision
Indicates a relationship where roles, responsibilities, or categories are separated or distinguished based on gender.
-
D.
genderConfiguration
Indicates how the genders of the involved entities are arranged or combined within a particular relationship or context.
-
E.
genderTarget
Indicates that an action, message, or effect is specifically directed toward entities of a particular gender.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5ee3213c8190af2853a2a5b302a2 |
completed | April 14, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:21 p.m.