Triple
T25223030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Indis |
E632012
|
entity |
| Predicate | positionOnEvangelization |
P103720
|
FINISHED |
| Object | rejects forced conversion |
—
|
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: rejects forced conversion | Statement: [De Indis, positionOnEvangelization, rejects forced conversion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnEvangelization Context triple: [De Indis, positionOnEvangelization, rejects forced conversion]
-
A.
hasEvangelizationFocus
chosen
Indicates that an entity is oriented toward or primarily concerned with evangelization activities or objectives.
-
B.
placeOfEvangelisticActivity
Indicates the location where evangelistic or missionary activities are carried out.
-
C.
activeAsEvangelistUntil
Indicates that an entity served in the role or function of an evangelist continuously up to a specified end time.
-
D.
positionOnLiturgy
Indicates the stance or viewpoint an entity holds regarding liturgical practices, forms, or regulations.
-
E.
positionOnChurchPower
Indicates a stance or viewpoint regarding the extent, role, or legitimacy of church authority or power.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 21, 2026, 1:03 p.m.