Triple
T5103959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglo-Catholicism |
E115045
|
entity |
| Predicate | maintainsWithin |
P31537
|
FINISHED |
| Object | Anglican tradition |
—
|
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: Anglican tradition | Statement: [Anglo-Catholicism, maintainsWithin, Anglican tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainsWithin Context triple: [Anglo-Catholicism, maintainsWithin, Anglican tradition]
-
A.
maintainedWithin
chosen
Indicates that one entity is kept, preserved, or sustained inside the boundaries or context of another entity.
-
B.
maintainsThrough
Indicates that one entity preserves, upholds, or continues a state, condition, or relationship by means of another specified entity, process, or medium.
-
C.
soughtToMaintain
Indicates an entity’s deliberate effort or intention to keep another entity or condition in its existing state over time.
-
D.
maintainedFor
Indicates that something is kept in a particular state, condition, or operation for the benefit, use, or purpose of another entity.
-
E.
parityMaintainedWith
Indicates that a state of equality or balance (such as value, status, or conditions) is preserved between two entities over time.
- 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_69bd4440b3348190be1251fd8b7951f1 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7588c1cc81909d380f91ee214808 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.