Triple
T36530122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friday mosque |
E900417
|
entity |
| Predicate | requiresLeader |
P37571
|
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: [Friday mosque, requiresLeader, imam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresLeader Context triple: [Friday mosque, requiresLeader, imam]
-
A.
requiresLeaderQualification
Indicates that an entity can only assume or perform a leadership role if a specified qualification or credential is met.
-
B.
requiresSimultaneousLeadershipIn
Indicates that an entity must be led or managed at the same time within the specified context, implying concurrent leadership is required in that domain or setting.
-
C.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
D.
involvesLeader
chosen
Indicates that the relationship or action includes or is carried out by an entity serving in a leadership role.
-
E.
supportedLeader
Indicates that one entity actively backed, endorsed, or provided assistance to a particular leader.
- 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_69f76e5eedb88190a393b8c623f71dd7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fffc783b648190bcd7df017514d206 |
completed | May 10, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69fffc03fa24819099e12413dc6e0afd |
completed | May 10, 2026, 3:31 a.m. |
Created at: May 3, 2026, 4:11 p.m.