Triple
T1340823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westminster Larger Catechism |
E28458
|
entity |
| Predicate | structureFeature |
P5048
|
FINISHED |
| Object | numbered questions and answers |
—
|
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: numbered questions and answers | Statement: [Westminster Larger Catechism, structureFeature, numbered questions and answers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structureFeature Context triple: [Westminster Larger Catechism, structureFeature, numbered questions and answers]
-
A.
withinFeature
Indicates that one entity is spatially contained inside or lies entirely within the bounds of another feature.
-
B.
skeletonFeature
Indicates that one entity is a structural or anatomical skeletal feature or component of another entity.
-
C.
stylingFeature
Indicates a visual or design-related characteristic applied to an entity, such as formatting, layout, or aesthetic treatment.
-
D.
structureStyle
Indicates the architectural or design style characterizing how a structure is built or formed.
-
E.
featureType
chosen
Indicates the specific kind or category of feature that characterizes or distinguishes an 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c21490488190b4281a16c87677d1 |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef3e8fc8190ac9a1ba9b5879483 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.