Triple
T3655143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulh-i Kul |
E77510
|
entity |
| Predicate | influencedPolicyOn |
P22482
|
FINISHED |
| Object | religious minorities |
—
|
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: religious minorities | Statement: [Sulh-i Kul, influencedPolicyOn, religious minorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influencedPolicyOn Context triple: [Sulh-i Kul, influencedPolicyOn, religious minorities]
-
A.
influencedPolicyArea
chosen
Indicates that one entity has affected, shaped, or guided the development, direction, or implementation of a particular policy area associated with another entity.
-
B.
politicalInfluenceIn
Indicates that an entity exerts or holds political influence within a specified place, jurisdiction, or political context.
-
C.
inspiredByPolicy
Indicates that an action, decision, or entity is motivated, guided, or shaped by a specific policy or set of policies.
-
D.
councilInfluenceOn
Indicates the degree or manner in which a council affects, shapes, or exerts power over another entity or outcome.
-
E.
seeksToInfluence
Indicates an entity’s intention or effort to affect, shape, or alter another entity’s behavior, decisions, or state.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3baf57c8190b72b5d1b910d9db6 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.