Triple
T5974440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mylapore (traditional) |
E132949
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | place associated with an apostle |
C1820
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: place associated with an apostle Context triple: [Mylapore (traditional), instanceOf, place associated with an apostle]
-
A.
church mentioned in the Book of Revelation
A church mentioned in the Book of Revelation is a Christian congregation or community addressed in Revelation’s letters, symbolizing both a historical local assembly and a spiritual type with specific strengths, weaknesses, and prophetic significance.
-
B.
New Testament location
A New Testament location is any geographical place, region, or city referenced in the New Testament that provides historical and narrative context for its events and teachings.
-
C.
Christian holy place
chosen
A Christian holy place is a location—such as a church, chapel, shrine, or site of religious significance—set apart for worship, prayer, and encounters with the divine within the Christian tradition.
-
D.
early Christian disciple
An early Christian disciple is a follower of Jesus in the first generations of the Christian movement who embraced his teachings, participated in the emerging church community, and helped spread the new faith.
-
E.
patriarch of Antioch
The patriarch of Antioch is the senior ecclesiastical leader and chief bishop of one of the ancient Christian sees centered in Antioch, historically overseeing doctrine, liturgy, and church governance for his jurisdiction.
- F. None of above.
Provenance (1 batch)
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_69c0086deab081908550159ca23eec9b |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:03 p.m.