Triple
T33919302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marriage Masterpeace |
E869557
|
entity |
| Predicate | hasThematicBasis |
P93696
|
FINISHED |
| Object | Christian faith |
—
|
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: Christian faith | Statement: [Marriage Masterpeace, hasThematicBasis, Christian faith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThematicBasis Context triple: [Marriage Masterpeace, hasThematicBasis, Christian faith]
-
A.
hasThematicOrigin
chosen
Indicates that something originates from, or is thematically derived from, a particular source, subject, or theme.
-
B.
hasThematicConcern
Indicates that one entity (such as a work, text, or discourse) centrally involves, addresses, or focuses on a particular theme, issue, or subject as a primary concern.
-
C.
hasCentralTheme
Indicates that one entity serves as the primary or dominant theme or subject matter of another entity.
-
D.
hasThematicPavilion
Indicates that an entity includes or is associated with a specific thematic pavilion as part of its structure or offerings.
-
E.
hasNotabilityBasis
Indicates that the notability or significance of one entity is based on, or derived from, another entity or factor.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: May 1, 2026, 1:49 a.m.