Triple
T25678767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baptist Churches in Northern India |
E643878
|
entity |
| Predicate | widerMovement |
P20165
|
FINISHED |
| Object | Ecumenical movement in India |
—
|
NE NERFINISHED |
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: Ecumenical movement in India | Statement: [Baptist Churches in Northern India, widerMovement, Ecumenical movement in India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: widerMovement Context triple: [Baptist Churches in Northern India, widerMovement, Ecumenical movement in India]
-
A.
widerUsage
Indicates that one entity is used or applied more broadly, frequently, or in a greater variety of contexts than another.
-
B.
typicalMovement
Indicates the usual or characteristic way in which an entity moves or is expected to move.
-
C.
Bewegung
Indicates a movement or change of position or location of an entity relative to a reference point or path.
-
D.
broaderMovement
chosen
Indicates that one movement is a more general, encompassing movement within which another, more specific movement is situated.
-
E.
width
Indicates the measurement of how wide an entity is, typically the extent of its horizontal dimension from side to side.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb77c3a08190b63e811dd21989fd |
completed | May 2, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 7:43 p.m.