Triple
T9619618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Velutha |
E232306
|
entity |
| Predicate | religionOfCommunityAroundHim |
P60821
|
FINISHED |
| Object | Syrian Christian |
—
|
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: Syrian Christian | Statement: [Velutha, religionOfCommunityAroundHim, Syrian Christian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionOfCommunityAroundHim Context triple: [Velutha, religionOfCommunityAroundHim, Syrian Christian]
-
A.
religiousBackgroundOfCommunity
chosen
Indicates the religious tradition, affiliation, or belief system that characterizes or predominates within a particular community.
-
B.
hostReligion
Indicates that an entity organizes, accommodates, or provides a venue for a particular religious group, event, or practice.
-
C.
sharesReligionWith
Indicates that two entities follow or are associated with the same religion or religious tradition.
-
D.
isCentralToReligion
Indicates that something plays a core, defining, or foundational role within a particular religion or religious tradition.
-
E.
influencedByReligion
Indicates that an entity’s characteristics, decisions, or development are shaped or affected by religious beliefs, practices, or institutions.
- 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_69ca84867bb88190b4b57dd5a56d5691 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9ad295008190a4418d092576cb53 |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:09 p.m.