Triple
T12250090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FMS |
E291948
|
entity |
| Predicate | associatedWithCharism |
P57647
|
FINISHED |
| Object | education |
—
|
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: education | Statement: [FMS, associatedWithCharism, education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCharism Context triple: [FMS, associatedWithCharism, education]
-
A.
sharesCharismWith
Indicates that two entities possess and express the same or very similar spiritual gift, mission, or distinctive inspirational quality.
-
B.
associatedWithChurch
Indicates a relationship in which an entity has a connection, involvement, or affiliation with a church.
-
C.
foundingCharism
chosen
Indicates the distinctive spiritual focus, mission, or guiding gift that characterizes the founding identity of a religious community or organization.
-
D.
associatedDevotion
Indicates a relationship where one entity is linked to or characterized by a particular devotion, dedication, or religious/spiritual practice connected to another entity.
-
E.
associatedWithSacrament
Indicates a relationship where something is connected or related to a specific sacrament in a religious or ritual context.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.