Triple
T37577159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augustana Theological Seminary |
E934853
|
entity |
| Predicate | focusCommunity |
P65912
|
FINISHED |
| Object | Swedish-American Lutherans |
—
|
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: Swedish-American Lutherans | Statement: [Augustana Theological Seminary, focusCommunity, Swedish-American Lutherans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusCommunity Context triple: [Augustana Theological Seminary, focusCommunity, Swedish-American Lutherans]
-
A.
focusFeature
Indicates that one entity is the primary or emphasized feature, aspect, or attribute being highlighted or concentrated on in relation to another.
-
B.
focusShift
Indicates a change in attention or emphasis from one entity or topic to another.
-
C.
focusMechanism
Indicates the method or process by which attention or emphasis is directed toward a particular entity or aspect within a context.
-
D.
focusable
Indicates that an entity can receive input focus or become the active target for user interaction or navigation.
-
E.
canonicalFocus
chosen
Indicates that one entity is the primary or most representative focus or point of attention in relation to 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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 3, 2026, 4:17 p.m.