Triple
T2709530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Lutheran Council |
E59823
|
entity |
| Predicate | cooperationModel |
P19448
|
FINISHED |
| Object | fellowship of autonomous churches |
—
|
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: fellowship of autonomous churches | Statement: [International Lutheran Council, cooperationModel, fellowship of autonomous churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cooperationModel Context triple: [International Lutheran Council, cooperationModel, fellowship of autonomous churches]
-
A.
cooperationType
chosen
Indicates the specific kind or form of cooperative relationship that exists between the related entities.
-
B.
collaborationModel
Indicates the type or structure of cooperative interaction or joint work established between entities.
-
C.
cooperationPartner
Indicates that two entities are engaged in a collaborative relationship, working together toward shared goals or mutual benefit.
-
D.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
E.
hasCooperative
Indicates that one entity participates in a cooperative relationship or partnership with another entity.
- 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda7542548190bbf6c947145f7f63 |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd8224c688190bb4a362360b03007 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.