Triple
T38635114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congregation of Jesus |
E937555
|
entity |
| Predicate | ministryField |
P191306
|
FINISHED |
| Object | schools |
—
|
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: schools | Statement: [Congregation of Jesus, ministryField, schools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ministryField Context triple: [Congregation of Jesus, ministryField, schools]
-
A.
ministry
Indicates that an entity serves as a governmental ministry responsible for specific public functions or policy areas in relation to another entity.
-
B.
ministryArea
Indicates that one entity is the geographic or administrative area over which a ministry or ministerial body has responsibility or jurisdiction.
-
C.
ministryUse
Indicates that an entity utilizes or is employed by a ministry (a governmental or religious administrative body) for its functions or purposes.
-
D.
formationMinistry
Indicates that an entity is responsible for or involved in establishing, organizing, or structuring a ministry or governmental department.
-
E.
methodOfMinistry
Indicates the specific way or approach through which ministry or religious service is carried out.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdb0cf6008190b27046b694f84356 |
completed | May 7, 2026, 6:33 p.m. |
Created at: May 3, 2026, 4:32 p.m.