Triple
T34789532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Low Church Anglicanism |
E1002906
|
entity |
| Predicate | oftenPrefers |
P60489
|
FINISHED |
| Object | memorialist view of Holy Communion |
—
|
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: memorialist view of Holy Communion | Statement: [Low Church Anglicanism, oftenPrefers, memorialist view of Holy Communion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenPrefers Context triple: [Low Church Anglicanism, oftenPrefers, memorialist view of Holy Communion]
-
A.
statedPreference
chosen
Indicates that one entity has explicitly expressed or declared a preference for another entity or option.
-
B.
prefersWater
Indicates a relationship where an entity favors or chooses water over other available options.
-
C.
contrastsPreferenceFor
Indicates a relationship where one entity’s preference is compared against and shown to differ from another entity’s preference.
-
D.
oftenHave
Indicates that one entity frequently possesses, experiences, or is associated with another entity.
-
E.
mostlyIn
Indicates that one entity is contained or located within another entity to a predominant or greater extent, though not necessarily entirely.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 3, 2026, 3:59 p.m.