Triple
T719562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dicastery for the Laity, Family and Life |
E14385
|
entity |
| Predicate | competenceArea |
P18508
|
FINISHED |
| Object | lay apostolate |
—
|
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: lay apostolate | Statement: [Dicastery for the Laity, Family and Life, competenceArea, lay apostolate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competenceArea Context triple: [Dicastery for the Laity, Family and Life, competenceArea, lay apostolate]
-
A.
competence
Indicates that an entity has the ability, skill, or qualification to perform a task or fulfill a role effectively.
-
B.
assessmentAreaDefinedBy
Indicates that the scope or domain of an assessment is specified or delimited by a particular area or boundary.
-
C.
hasCompetence
Indicates that an entity possesses the ability, skill, or qualification to perform a specific task or function effectively.
-
D.
attainmentAreaDefinedBy
Indicates that the scope or domain in which an attainment applies is specified or delimited by a particular area or context.
-
E.
fieldOfWork
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a58e65e8819098cba7e6a20d8f33 |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f513608190b716b939d574c292 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a57267c481909790a1fda3fced08 |
completed | March 1, 2026, 8:45 p.m. |
Created at: March 1, 2026, 7:37 p.m.