Triple
T6856932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mosque Foundation |
E158168
|
entity |
| Predicate | hasReligiousLeaderType |
P3092
|
FINISHED |
| Object | imam |
—
|
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: imam | Statement: [Mosque Foundation, hasReligiousLeaderType, imam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousLeaderType Context triple: [Mosque Foundation, hasReligiousLeaderType, imam]
-
A.
hasClergyType
chosen
Indicates the specific category or role of clergy associated with an entity.
-
B.
hasReligiousCharacter
Indicates that an entity possesses a religious nature, function, or affiliation, or is characterized by religious aspects or significance.
-
C.
religiousFigureType
Indicates the specific role or category of a person recognized as a religious figure (e.g., priest, monk, prophet) within a religious context.
-
D.
spiritualLeaderOf
Indicates that one entity serves as the primary religious or spiritual guide, authority, or mentor for another entity or group.
-
E.
hasReligiousFigureAssociation
Indicates a relationship in which an entity is connected or linked to a religious figure, such as through dedication, representation, influence, or affiliation.
- 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6da3ce95081909a424ac04bc7fa07 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b168908190b2f7c724b1bc7fc9 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:21 p.m.