Triple
T23822410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gnesio-Lutherans |
E589270
|
entity |
| Predicate | coreAim |
P107597
|
FINISHED |
| Object | defend original doctrines of Martin Luther |
—
|
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: defend original doctrines of Martin Luther | Statement: [Gnesio-Lutherans, coreAim, defend original doctrines of Martin Luther]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreAim Context triple: [Gnesio-Lutherans, coreAim, defend original doctrines of Martin Luther]
-
A.
hasCoreAim
chosen
Indicates that something possesses a primary, central objective or purpose that guides its overall direction or activity.
-
B.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
C.
centralGoal
Indicates that something is the primary objective or main aim around which other actions, plans, or considerations are organized.
-
D.
coreIdeal
Indicates that something is a fundamental, central principle or value that defines or strongly guides another entity.
-
E.
core
Indicates a central, most important, or foundational part of something in relation to its surrounding or supporting elements.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7afff6c819096a0af7e008ea8d4 |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:59 p.m.