Triple
T18091048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spiritual Franciscans |
E432966
|
entity |
| Predicate | religiousVowEmphasis |
P15112
|
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: [Spiritual Franciscans, religiousVowEmphasis, poverty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousVowEmphasis Context triple: [Spiritual Franciscans, religiousVowEmphasis, poverty]
-
A.
religiousMood
Indicates a prevailing emotional or spiritual atmosphere associated with religious experience, practice, or devotion between entities.
-
B.
doctrinalEmphasis
chosen
Indicates a relationship where a doctrine, belief system, or teaching is given particular focus, priority, or stress within a religious, ideological, or organizational context.
-
C.
religiousPhraseOptional
Indicates that a religious phrase may be present in the context but is not required.
-
D.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
E.
tookReligiousVows
Indicates that an entity formally committed to a religious life by taking recognized vows within a religious tradition.
- 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dd18b55081909c416fb7186bd4a4 |
completed | April 19, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:27 a.m.