Triple
T2027960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evangelical churches |
E44450
|
entity |
| Predicate | priority |
P25884
|
FINISHED |
| Object | church planting |
—
|
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: church planting | Statement: [Evangelical churches, priority, church planting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: priority Context triple: [Evangelical churches, priority, church planting]
-
A.
missionPriority
Indicates the relative level of importance or urgency assigned to a mission compared to other missions or tasks.
-
B.
parity
Indicates that two quantities share the same evenness or oddness, or more generally that they have equivalent status or value in a given context.
-
C.
primaryCriterion
Indicates that one factor is designated as the main or most important basis for a decision, judgment, or selection among alternatives.
-
D.
typeOfPriority
chosen
Indicates the specific priority level or category assigned to something relative to other items or tasks.
-
E.
precision
Indicates the degree to which an action, measurement, or outcome is carried out with exactness, minimal deviation, and fine-grained accuracy.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb911e5dc819097e40af0da4d01e7 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.