Triple
T2861273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Candler School of Theology |
E63326
|
entity |
| Predicate | denominationalTradition |
P25565
|
FINISHED |
| Object | Methodist |
—
|
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: Methodist | Statement: [Candler School of Theology, denominationalTradition, Methodist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denominationalTradition Context triple: [Candler School of Theology, denominationalTradition, Methodist]
-
A.
theologicalTradition
Indicates the religious or doctrinal school, lineage, or system of belief within which an entity’s theology is developed or practiced.
-
B.
denominations
Indicates the specific units or categories into which something (often money, values, or items) is divided or classified.
-
C.
denominationalOrientation
chosen
Indicates the specific religious denomination or sect with which an entity is formally affiliated or aligned.
-
D.
hasRiteOrTradition
Indicates that an entity is associated with, practices, or observes a particular rite, ritual, or tradition.
-
E.
hasDenominationalCounterpart
Indicates that one entity has a corresponding or equivalent entity in another religious denomination or branch.
- 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_69ab4c41e8c08190a9e8f5249cc12610 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf8df8288190816767169ea7cbf9 |
completed | March 7, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69abdd123ec48190af50a1859aea50b7 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.