Triple
T2605294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muscular Christianity |
E58643
|
entity |
| Predicate | hasCoreTheme |
P6627
|
FINISHED |
| Object | physical strength as a Christian virtue |
—
|
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: physical strength as a Christian virtue | Statement: [Muscular Christianity, hasCoreTheme, physical strength as a Christian virtue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreTheme Context triple: [Muscular Christianity, hasCoreTheme, physical strength as a Christian virtue]
-
A.
hasCentralTheme
chosen
Indicates that one entity serves as the primary or dominant theme or subject matter of another entity.
-
B.
hasThemeConnection
Indicates a relationship where one entity is linked to another through a shared or related theme, topic, or conceptual focus.
-
C.
hasCoreState
Indicates that an entity possesses or is associated with a fundamental or primary state that defines its core condition or behavior.
-
D.
hasCoreValue
Indicates that an entity possesses or is characterized by a fundamental guiding principle or core belief.
-
E.
containsThemeArea
Indicates that one entity includes or encompasses a specific thematic area as part of its scope or content.
- 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_69ab4ac3523881909679750c9f8c2dec |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd8def9bc8190b2e013abffc7b191 |
completed | March 7, 2026, 7:50 a.m. |
| PD | Predicate disambiguation | batch_69abd80ab7248190ba06ba14fe4c5638 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:49 p.m.