Triple
T24997294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franciscan family |
E625606
|
entity |
| Predicate | hasCoreCharism |
P57647
|
FINISHED |
| Object | poverty |
—
|
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: poverty | Statement: [Franciscan family, hasCoreCharism, poverty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreCharism Context triple: [Franciscan family, hasCoreCharism, poverty]
-
A.
sharesCharismWith
Indicates that two entities possess and express the same or very similar spiritual gift, mission, or distinctive inspirational quality.
-
B.
foundingCharism
chosen
Indicates the distinctive spiritual focus, mission, or guiding gift that characterizes the founding identity of a religious community or organization.
-
C.
hasReligiousCharismAssociatedWith
Indicates that an entity possesses or is identified with a particular religious charism, spiritual gift, or distinctive spiritual focus associated with another entity.
-
D.
hasCharm
Indicates that an entity possesses or exhibits charm, attractiveness, or an appealing quality.
-
E.
hasDoctrinalCharacteristic
Indicates that an entity possesses a specific doctrinal feature, quality, or attribute within a belief or teaching system.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 18, 2026, 6:04 a.m.